From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Fix bootwrapper builds with newer gcc versions
Date: Fri, 2 May 2008 13:54:15 +0200 [thread overview]
Message-ID: <bfc75e2dc32ba86b93751cb21df97e56@kernel.crashing.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0805020311310.28690@blarg.am.freescale.net>
> GCC 4.4.x looks to be adding support for generating out-of-line
> register
> saves/restores based on:
>
> http://gcc.gnu.org/ml/gcc-patches/2008-04/msg01678.html
>
> This breaks the bootwrapper as we'd need to link with libgcc to get the
> implementation of the register save/restores.
>
> To workaround this issue, we just stole the save/restore code from gcc
> and simplified it down for our needs (integer only).
Why can't we link with libgcc, instead?
Segher
next prev parent reply other threads:[~2008-05-02 11:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 8:11 [PATCH] [POWERPC] Fix bootwrapper builds with newer gcc versions Kumar Gala
2008-05-02 11:54 ` Segher Boessenkool [this message]
2008-05-02 13:28 ` Kumar Gala
2008-05-02 13:37 ` Segher Boessenkool
2008-05-02 13:41 ` Kumar Gala
2008-05-02 15:20 ` Scott Wood
2008-05-02 17:15 ` Segher Boessenkool
2008-05-02 14:09 ` Kumar Gala
2008-05-02 17:11 ` Segher Boessenkool
2008-05-02 21:28 ` Kumar Gala
2008-05-02 21:40 ` David Miller
2008-05-02 21:58 ` Kumar Gala
2008-05-02 23:27 ` Benjamin Herrenschmidt
2008-05-02 23:38 ` David Miller
2008-05-03 0:06 ` Segher Boessenkool
2008-05-03 7:50 ` Benjamin Herrenschmidt
2008-05-03 7:55 ` David Miller
2008-05-03 11:01 ` Benjamin Herrenschmidt
2008-05-05 11:55 ` Gabriel Paubert
2008-05-02 12:13 ` Josh Boyer
2008-05-02 13:32 ` Kumar Gala
2008-05-02 13:53 ` Josh Boyer
2008-05-02 13:59 ` 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=bfc75e2dc32ba86b93751cb21df97e56@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--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).