From: Richard Guenther <rguenther@suse.de>
To: "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu>
Cc: Nathan Froyd <froydnj@codesourcery.com>,
gcc-patches@gcc.gnu.org, janis187@us.ibm.com,
zadeck@naturalbridge.com
Subject: Re: [PATCH,testsuite] fix gcc.dg/tree-ssa/20030714-1.c with -fPIC
Date: Thu, 24 Jan 2008 13:24:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0801241019160.23003@zhemvz.fhfr.qr> (raw)
In-Reply-To: <Pine.GSO.4.58.0801240302320.11155@caipclassic.rutgers.edu>
On Thu, 24 Jan 2008, Kaveh R. GHAZI wrote:
> On Wed, 23 Jan 2008, Richard Guenther wrote:
>
> > Backporting Kennys patch is the right thing to do - I don't know
> > why the PR was closed as fixed.
>
> Ok, patch below was tested against 4.2 on x86_64-unknown-linux-gnu, no
> regressions.
>
> Testing on 4.1 on i686 completed bootstrap and the testsuite is in
> progress.
>
> Okay for 4.2, (and 4.1 assuming testsuite finished okay)?
Ok.
Thanks,
Richard.
prev parent reply other threads:[~2008-01-24 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 21:40 Nathan Froyd
2008-01-24 1:09 ` Kaveh R. GHAZI
2008-01-24 1:54 ` Richard Guenther
2008-01-24 11:30 ` Kaveh R. GHAZI
2008-01-24 13:24 ` Richard Guenther [this message]
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=Pine.LNX.4.64.0801241019160.23003@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=froydnj@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
--cc=janis187@us.ibm.com \
--cc=zadeck@naturalbridge.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).