Use ccache so that it recompiles faster after a make clean.

Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>
Signed-off-by: Dan Trifan <jimsth@gmail.com>
makefile: some build tweaks

Signed-off-by: Dan Trifan <jimsth@gmail.com>

Conflicts:
	Makefile
makefile: add Werror-implicit-function-declaration

Signed-off-by: Dan Trifan <jimsth@gmail.com>
Makefile: change build flags

Signed-off-by: Dan Trifan <jimsth@gmail.com>

Conflicts:
	arch/arm/Makefile
Makefile: remove 'mythical' build flags

1) The root's and the arch's Makefile do not both need to
contain the same build flags. The root's Makefile inherits
the arch's flags.

2) It is unnecessary to define the -mfpu=X flag, since the
arch's Makefile sets -msoft-float, which excludes the usage
of hardware vfp units.

3) Automatic vectorization via -ftree-vectorize does not
work with -msoft-float. Even if it were working, automatic
vectorization does not give noteworthy improvements in
performance.

4) In arch/arm/vfp/Makefile, it is counter-productive to
change the -mfpu=X assembler flag, since there's no hardware
vfp usable, as pointed out before.

Information sources:
  https://wiki.debian.org/ArmHardFloatPort/VfpComparison

  https://lkml.org/lkml/2011/10/3/254

Signed-off-by: Dan Trifan <jimsth@gmail.com>
Makefile: Add Config Variable Os - O2 - O3 for choice Compilation

Conflicts:
	Makefile
 makefile: add config for graphite optimizations (synergydev)

makefile: add link-time optimization (synergydev)
makefile update
makefile flags and memset

Conflicts:
	arch/arm/vfp/Makefile
 Turn off -Wmaybe-uninitialized when building with -Os

gcc-4.7 and higher add a lot of false positive warnings about
potential uses of uninitialized warnings, but only when optimizing
for size (-Os). This is the default when building allyesconfig,
which turns on CONFIG_CC_OPTIMIZE_FOR_SIZE.

In order to avoid getting a lot of patches that initialize such
variables and accidentally hide real errors along the way, let's
just turn off this warning on the respective gcc versions
when building with size optimizations. The -Wmaybe-uninitialized
option was introduced in the same gcc version (4.7) that is now
causing the false positives, so there is no effect on older compilers.

A side effect is that when building with CONFIG_CC_OPTIMIZE_FOR_SIZE,
we might now see /fewer/ warnings about possibly uninitialized
warnings than with -O2, but that is still much better than seeing
warnings known to be bogus.
compile with ccache
Makefile : use hard-float
arm: vfp: use hard-float & neon
Revert "Makefile : use hard-float"

This reverts commit 2b2f5702c83f1bf1ac2019a9a05d3c23657a9d9c.

Conflicts:
	arch/arm/boot/zImage
Makefile changes

Conflicts:
	arch/arm/boot/zImage
more makefile tweaks

Conflicts:
	arch/arm/boot/zImage
makefile: remove repetitive cflags
makefile : minor changes
add Graphite to Host
 when compiling with graphite as well

Conflicts:
	arch/arm/boot/zImage
Revert "ARM: keep __my_cpu_offset consistent with generic one"

This reverts commit abe8ecff963d23f0bb42b92b7b7e6bb0c3b651e1.