From: Nathan Froyd <froydnj@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Matthias Klose <doko@ubuntu.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Paolo Carlini <paolo.carlini@oracle.com>,
GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: [patch] PR40134, use a linker script on arm-linux to link with -lgcc_s -lgcc
Date: Tue, 07 Jul 2009 13:22:00 -0000 [thread overview]
Message-ID: <20090707132053.GO11286@codesourcery.com> (raw)
In-Reply-To: <20090707091425.GB4462@tyan-ft48-01.lab.bos.redhat.com>
On Tue, Jul 07, 2009 at 11:14:25AM +0200, Jakub Jelinek wrote:
> On Tue, Jul 07, 2009 at 11:03:24AM +0200, Matthias Klose wrote:
> > Use a linker script to link with -lgcc_s -lgcc on arm-linux, which allows the
> > arm-linux target to run the testsuite without regressions with the patch for the
> > exception propagation support [1] enabled.
> >
> > The approach taken is the same as used on the sh-linux configuration.
>
> For branch I think this could be acceptable, but for trunk I really think
> we should do this on all architectures that have shared libgcc_s*.
> It is not just arm/sh that need this, but also e.g. ppc-linux (and maybe
> ppc64-linux), where libgcc.a only contains the out of line gpr/fpr register
> save/restores.
The patch isn't needed for ppc64-linux, because the linker synthesizes
the necessary routines when necessary. The code for emitting out of
line saves/restores is actually broken at the moment, but the patch to
fix the brokenness can't be committed because of the above issue.
-Nathan
next prev parent reply other threads:[~2009-07-07 13:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 9:10 Matthias Klose
2009-07-07 9:56 ` Jakub Jelinek
2009-07-07 11:51 ` Dave Korn
2009-07-07 12:21 ` Jakub Jelinek
2009-07-07 13:45 ` Dave Korn
2009-07-07 13:52 ` H.J. Lu
2009-07-07 15:30 ` Dave Korn
2009-07-07 15:53 ` H.J. Lu
2009-07-07 13:22 ` Nathan Froyd [this message]
2009-07-10 7:01 ` Matthias Klose
2009-07-10 7:56 ` Jakub Jelinek
2009-07-13 13:43 ` Matthias Klose
2009-09-09 11:24 ` Jakub Jelinek
2009-09-09 12:27 ` Joseph S. Myers
2009-09-09 13:25 ` Jakub Jelinek
2009-09-09 19:50 ` Richard Henderson
2009-09-09 20:56 ` Joseph S. Myers
2009-09-11 17:13 ` Matthias Klose
2009-09-22 12:26 ` [ping] " Matthias Klose
2009-09-22 15:57 ` Andrew Haley
2009-09-24 8:26 ` Matthias Klose
2009-09-24 8:49 ` Andrew Haley
2009-09-24 10:07 ` Matthias Klose
2009-09-24 10:45 ` Andrew Haley
2009-10-14 15:15 ` Richard Earnshaw
[not found] ` <1255527525.4842.29.camel@e200601-lin.cambridge.arm.com>
2009-10-21 14:11 ` Matthias Klose
2009-10-30 0:22 ` [ping2] " Matthias Klose
2009-10-30 0:55 ` Paolo Carlini
2009-11-02 16:02 ` Matthias Klose
2009-11-02 16:33 ` Paolo Carlini
2009-11-12 18:21 ` Matthias Klose
2009-11-12 18:47 ` Paolo Carlini
2009-12-09 10:47 ` Matthias Klose
2009-12-09 10:50 ` Paolo Carlini
2009-12-09 10:58 ` Paolo Carlini
2009-12-11 8:48 ` Matthias Klose
2009-12-11 10:00 ` Paolo Carlini
2009-12-14 1:34 ` Matthias Klose
2009-12-11 10:35 ` Joseph S. Myers
2009-11-16 22:47 ` Ralf Wildenhues
2009-11-16 22:48 ` Paolo Carlini
2009-09-09 18:29 David Edelsohn
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=20090707132053.GO11286@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=java-patches@gcc.gnu.org \
--cc=paolo.carlini@oracle.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 read-only IMAP folder(s) and NNTP newsgroup(s).