From: Paolo Carlini <paolo.carlini@oracle.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
Andrew Haley <aph@redhat.com>, Jakub Jelinek <jakub@redhat.com>,
Alexandre Oliva <aoliva@redhat.com>,
Nathan Froyd <froydnj@codesourcery.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: [ping2] Re: [ping] Re: [patch] PR40134, use a linker script on arm-linux to link with -lgcc_s -lgcc
Date: Fri, 11 Dec 2009 10:00:00 -0000 [thread overview]
Message-ID: <4B221797.4050703@oracle.com> (raw)
In-Reply-To: <4B21C863.405@ubuntu.com>
On 12/11/2009 05:19 AM, Matthias Klose wrote:
> the attached patch enables the link tests on linux, kfreebsd, and hurd
> targets. checked with the (Debian) kfreebsd and hurd maintainers that
> this is the right thing to do (although there doesn't exist an active
> port of these on arm or hppa. tested on i486-linux-gnu,
> arm-linux-gnueabi and hppa-linux-gnu. ok for the trunk?
First, thanks Matthias for your patience on this issue.
The patch looks very nice to me, just wait one day or so for comments
and then go ahead, patch is approved for mainline.
If you want, I would suggest adding a one-line comment in the code, say,
after " # Do link tests if possible, instead asm tests, limited to some
platforms", mentioning the PRs, these thorny issues about libgcc...
Thanks again,
Paolo.
next prev parent reply other threads:[~2009-12-11 9:58 UTC|newest]
Thread overview: 41+ 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
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 [this message]
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
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=4B221797.4050703@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=Richard.Earnshaw@arm.com \
--cc=aoliva@redhat.com \
--cc=aph@redhat.com \
--cc=doko@ubuntu.com \
--cc=froydnj@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=java-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).