From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Remove gcc configure option --enable-target-optspace for powerpc
Date: Mon, 25 Jan 2010 00:37:12 -0800 [thread overview]
Message-ID: <20100125083712.GB26355@gmail.com> (raw)
In-Reply-To: <ac9c93b11001250015h1a8c325fk1eb13229924c40b8@mail.gmail.com>
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
prev parent reply other threads:[~2010-01-25 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 8:10 [RFC] Remove gcc configure option --enable-target-optspace for powerpc Khem Raj
2010-01-25 8:15 ` Frans Meulenbroeks
2010-01-25 8:37 ` Khem Raj [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100125083712.GB26355@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.