[Buildroot] [PATCH v4] gcc: explicitly use C{XX}FLAGS_FOR_TARGET instead of --enable-target-optspace

Alexey Brodkin Alexey.Brodkin at synopsys.com
Tue Sep 23 11:10:16 UTC 2014


Hi Thomas,

On Mon, 2014-09-15 at 17:29 +0400, Alexey Brodkin wrote:
> Hi Thomas,
> 
> On Mon, 2014-09-08 at 09:53 +0400, Alexey Brodkin wrote:
> > Hi Thomas,
> > 
> > On Mon, 2014-09-01 at 11:55 +0400, Alexey Brodkin wrote:
> > > From: Alexey Brodkin <Alexey.Brodkin at synopsys.com>
> > > 
> > > 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 at synopsys.com>
> > > 
> > > Cc: Anton Kolesov <akolesov at synopsys.com>
> > > Cc: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
> > > Cc: Peter Korsgaard <peter at korsgaard.com>
> > > Cc: Gustavo Zacarias <gustavo at zacarias.com.ar>
> > > ---
> > > 
> > > Compared to v3 use "=" instead of ":=" which is not actually required here.
> > 
> > I'm wondering if this version is fine and we may go ahead an apply it?
> 
> Please treat this as a polite reminder about this pending patch.

Any chance for this change to made its way into upstream Buildroot?

-Alexey



More information about the buildroot mailing list