gcc: explicitly use C{XX}FLAGS_FOR_TARGET instead of --enable-target-optspace
authorAlexey Brodkin <Alexey.Brodkin@synopsys.com>
Tue, 24 Mar 2015 13:55:15 +0000 (16:55 +0300)
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Wed, 22 Jul 2015 21:20:50 +0000 (23:20 +0200)
commit0fe633cdff66febadc50bab3e0af4b3be53811c8
treed1684f5a3e78202f1889a2fa14b544abacc6d2a4
parent64c10ae691e230935473f23ef71ab997293adf8f
gcc: explicitly use C{XX}FLAGS_FOR_TARGET instead of --enable-target-optspace

The gcc.mk file is passing --enable-target-optspace to gcc configure
script, to ask for space-optimized (-Os) target libraries. However,
passing this option has the effect of overriding any custom
CFLAGS_FOR_TARGET or CXXFLAGS_FOR_TARGET values that may be passed.

These are some situations when it is required to pass custom flags on
buildong
of libgcc:
 * Default flags "-g -Os" lead to build isses as with PowerPC on gcc 4.5
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43810)
 * Particular CPU requires specific instructions for HW support
 * Deep optimizations

Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Cc: Anton Kolesov <akolesov@synopsys.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Peter Korsgaard <peter@korsgaard.com>
Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
package/gcc/gcc.mk