From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Fix kernel builds with newer gcc versions and -Os
Date: Fri, 2 May 2008 19:34:23 +0200 [thread overview]
Message-ID: <03e9cbca081bff8f6db9862bf3d8d028@kernel.crashing.org> (raw)
In-Reply-To: <F62A680D-C2D8-42B0-B4D6-F3A00F228EB1@kernel.crashing.org>
>> <brokenrecord>
>> Why don't we just link with libgcc?
>> </brokenrecord>
>
> Its something of a PITA to do that in the kernel at this point since
> we've duplicated libgcc functionality in it. I'm sure there are some
> historical reasons this wasn't done to start with.
That's the same as saying that it would be a nice cleanup to remove all
that duplicated code now...
Segher
next prev parent reply other threads:[~2008-05-02 17:34 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 [this message]
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
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=03e9cbca081bff8f6db9862bf3d8d028@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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).