From: Scott Wood <scottwood@freescale.com>
To: David Miller <davem@davemloft.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Fix kernel builds with newer gcc versions and -Os
Date: Fri, 02 May 2008 17:16:07 -0500 [thread overview]
Message-ID: <481B92A7.3070302@freescale.com> (raw)
In-Reply-To: <20080502.150448.32652665.davem@davemloft.net>
David Miller wrote:
> The problem only occurs once you reference a function that references
> libc stuff, and those guys are just lucky so far.
Yeah, lucky they don't need to reinvent the wheel every time the
GCC/libgcc interface changes. :-)
If GCC generates a call to a libgcc function that calls a libc function,
I'd consider that a pretty serious bug, given that said libc function is
likely to consist of GCC-generated code, which could call the same
libgcc function, which calls the libc function, etc.
> It's also one less variable to debug if you put the implementation
> in the kernel, or do you like debugging compiler induced problems?
> I don't :-)
I'd say problems are more likely if you use nonstandard implementations
of GCC internals...
-Scott
next prev parent reply other threads:[~2008-05-02 22:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 14:21 [PATCH] [POWERPC] Fix kernel builds with newer gcc versions and -Os Kumar Gala
2008-05-02 15:07 ` Scott Wood
2008-05-02 15:26 ` Kumar Gala
2008-05-02 17:34 ` Segher Boessenkool
2008-05-02 21:34 ` Kumar Gala
2008-05-02 21:40 ` Scott Wood
2008-05-02 21:42 ` David Miller
2008-05-02 21:45 ` Scott Wood
2008-05-02 22:04 ` David Miller
2008-05-02 22:16 ` Scott Wood [this message]
2008-05-02 22:30 ` David Miller
2008-05-02 22:38 ` Scott Wood
2008-05-02 22:39 ` David Miller
2008-05-03 0:15 ` Segher Boessenkool
2008-05-02 23:24 ` Benjamin Herrenschmidt
2008-05-02 23:23 ` Benjamin Herrenschmidt
2008-05-08 6:26 ` Paul Mackerras
2008-05-02 17:33 ` Segher Boessenkool
2008-05-02 21:31 ` Kumar Gala
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=481B92A7.3070302@freescale.com \
--to=scottwood@freescale.com \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).