From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] x86: Do no use reparm as it break libgcc linkage
Date: Wed, 9 Nov 2011 23:13:24 -0500 [thread overview]
Message-ID: <201111092313.25335.vapier@gentoo.org> (raw)
In-Reply-To: <CALButCKjiUQGfHLj6WSbteVM3n-NMnDe7K713VEv=HA6L3tcZw@mail.gmail.com>
On Wednesday 09 November 2011 16:42:51 Graeme Russ wrote:
> On Thu, Nov 10, 2011 at 4:12 AM, Mike Frysinger wrote:
> > On Wednesday 09 November 2011 05:32:59 Graeme Russ wrote:
> >> --- a/arch/x86/config.mk
> >> +++ b/arch/x86/config.mk
> >>
> >> -PLATFORM_CPPFLAGS += -mregparm=3
> >> -PLATFORM_CPPFLAGS += -fomit-frame-pointer
> >
> > this sounds like you're throwing the baby out with the bath water.
> > doesn't this severely affect the generated code ?
>
> No - omit-frame-pointer is enabled by -O2 and also:
>
> http://gcc.gnu.org/gcc-4.6/changes.html
>
> "The default setting (when not optimizing for size) for 32-bit
> GNU/Linux and Darwin x86 targets has been changed to
> -fomit-frame-pointer. The default can be reverted to
> -fno-omit-frame-pointer by configuring GCC with the
> --enable-frame-pointer configure option."
>
> So the flag is a do-nothing
ok, except:
- we build u-boot with -Os and not -O2
- i'd say most people aren't using gcc-4.6
i was referring also to throwing away -mregparm=3 ...
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20111109/2aae86ce/attachment.pgp
next prev parent reply other threads:[~2011-11-10 4:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 9:27 [U-Boot] [PATCH] [x86] Wrap small helper functions from libgcc to avoid an ABI mismatch Gabe Black
2011-11-08 13:33 ` Mike Frysinger
2011-11-08 22:27 ` Gabe Black
2011-11-08 22:34 ` [U-Boot] [PATCH v2] x86: " Gabe Black
2011-11-08 23:14 ` Graeme Russ
2011-11-09 4:49 ` Mike Frysinger
2011-11-09 3:57 ` Graeme Russ
2011-11-09 5:34 ` Mike Frysinger
2011-11-17 9:01 ` [U-Boot] [PATCH v3] " Gabe Black
2011-11-17 9:13 ` Gabe Black
2011-11-30 11:03 ` Graeme Russ
2011-11-09 3:05 ` [U-Boot] [PATCH v2] " Graeme Russ
2011-11-09 10:32 ` [U-Boot] [RFC] x86: Do no use reparm as it break libgcc linkage Graeme Russ
2011-11-09 17:12 ` Mike Frysinger
2011-11-09 21:42 ` Graeme Russ
2011-11-10 4:13 ` Mike Frysinger [this message]
2011-11-10 4:22 ` Graeme Russ
2011-11-10 5:10 ` Graeme Russ
2011-11-10 17:15 ` Mike Frysinger
2011-11-10 22:53 ` Graeme Russ
2011-11-11 0:23 ` Mike Frysinger
2011-11-11 1:23 ` Graeme Russ
2011-11-11 1:40 ` Mike Frysinger
2011-11-11 1:51 ` Graeme Russ
2011-11-11 1:55 ` Mike Frysinger
2011-11-11 1:59 ` Graeme Russ
2011-11-11 2:10 ` Gabe Black
2011-11-11 2:22 ` Graeme Russ
2011-11-11 2:41 ` Gabe Black
2011-11-11 4:49 ` Graeme Russ
2011-11-11 5:04 ` Mike Frysinger
2011-11-11 5:16 ` Graeme Russ
2011-11-11 16:24 ` Mike Frysinger
2011-11-11 2:44 ` Mike Frysinger
2011-11-11 19:59 ` Scott Wood
2011-11-16 23:00 ` Graeme Russ
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=201111092313.25335.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox