[RFC] Remove gcc configure option --enable-target-optspace for powerpc

[RFC] Remove gcc configure option --enable-target-optspace for powerpc

[Khem Raj]

Hi

I have run into a problem where compiling libgcc with -Os for powerpc SPE
targets caused some symols like _restgpr_Y_x to be referenced in
libgcc_s.so.1 due to gcc generating them for out-of-line prologues which
happens with Os. But these symbols are defined in libgcc.a so when linking 
a shared library which uses libgcc we get errors from linker complaining
that DSO is accessing a hidden symbol from libgcc.a which is a static
archive.

I thought we could remove --enable-target-optspace. In general it is only
used to compiling the gcc libraries e.g. libgcc libstdc++ etc. in OE
context so its not of a much hit on space usage if we let this option go
which would mean that these libraries would be compiled with -O2

I propose to remove this option for all powerpc and we can still leave it
in for other architectures. 

Does this sound reasonable ?

Thanks

-Khem

Re: [RFC] Remove gcc configure option --enable-target-optspace for powerpc

[Frans Meulenbroeks]

2010/1/25 Khem Raj <raj.khem@gmail.com>:
> Hi
>
> I have run into a problem where compiling libgcc with -Os for powerpc SPE
> targets caused some symols like _restgpr_Y_x to be referenced in
> libgcc_s.so.1 due to gcc generating them for out-of-line prologues which
> happens with Os. But these symbols are defined in libgcc.a so when linking
> a shared library which uses libgcc we get errors from linker complaining
> that DSO is accessing a hidden symbol from libgcc.a which is a static
> archive.
>
> I thought we could remove --enable-target-optspace. In general it is only
> used to compiling the gcc libraries e.g. libgcc libstdc++ etc. in OE
> context so its not of a much hit on space usage if we let this option go
> which would mean that these libraries would be compiled with -O2
>
> I propose to remove this option for all powerpc and we can still leave it
> in for other architectures.
>
> Does this sound reasonable ?

What about just removing the option when building libgcc for ppc ?

Frans

Re: [RFC] Remove gcc configure option --enable-target-optspace for powerpc

[Khem Raj]

On (25/01/10 09:15), Frans Meulenbroeks wrote:
> 2010/1/25 Khem Raj <raj.khem@gmail.com>:
> > Hi
> >
> > I have run into a problem where compiling libgcc with -Os for powerpc SPE
> > targets caused some symols like _restgpr_Y_x to be referenced in
> > libgcc_s.so.1 due to gcc generating them for out-of-line prologues which
> > happens with Os. But these symbols are defined in libgcc.a so when linking
> > a shared library which uses libgcc we get errors from linker complaining
> > that DSO is accessing a hidden symbol from libgcc.a which is a static
> > archive.
> >
> > I thought we could remove --enable-target-optspace. In general it is only
> > used to compiling the gcc libraries e.g. libgcc libstdc++ etc. in OE
> > context so its not of a much hit on space usage if we let this option go
> > which would mean that these libraries would be compiled with -O2
> >
> > I propose to remove this option for all powerpc and we can still leave it
> > in for other architectures.
> >
> > Does this sound reasonable ?
> 
> What about just removing the option when building libgcc for ppc ?

Yes its possible I guess although wont be as straight forward plus I did
not want to muck with gcc configury when we have options to control it.



> 
> Frans
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel