gcc: fix build with gcc 4.4.3 and DEBUG_INFO

gcc can produce a Segmentation fault when using DEBUG_INFO_REDUCED
see linux-kbuild.git : https://patchwork.kernel.org/patch/2113601/

From: Andi Kleen <ak@linux.intel.com>

Newer gcc enables the var-tracking pass with -g to keep track which
registers contain which variables. This is one of the slower passes in gcc.

With reduced debug info (aimed at objdump -S, but not using a full debugger)
we don't need this fine grained tracking. But it was still enabled
because -g was enabled. Disable it explicitely for DEBUG_INFO_REDUCED.

On my 8T workstation this gives me about a 12 second gain in building
a reasonable kernel config (2min16 vs 2min28) with DEBUG_INFO_REDUCED.
With full DEBUG_INFO it takes 2min46

The actual improvement in user time taken by the compiler is much higher
(all CPU combined user time 15min5s vs 16m30 before)
but the usual amdahl bottleneck on the linker prevents more speedup.
It still saves some more energy and keeps cycles for other things.

Signed-off-by: Andi Kleen <ak@linux.intel.com>

---------------------------------------------------------------------------

Also, recently added f_fs.c in android gadget is not compatible with
the -g option of CONFIG_DEBUG_INFO :
  internal compiler error: in dwarf2out_finish, at dwarf2out.c:18906

so, remove the -g only on android gadget object

Signed-off-by: Tanguy Pruvot <tanguy.pruvot@gmail.com>