From: "H.J. Lu" <hjl.tools@gmail.com>
To: Peter Bergner <bergner@vnet.ibm.com>
Cc: Richard Sandiford <rsandifo@nildram.co.uk>,
gcc-patches <gcc-patches@gcc.gnu.org>, Jeff Law <law@redhat.com>
Subject: Re: [PING H.J. Lu] Re: [PATCH] PR35371 GCSE loses track of REG_POINTER attribute
Date: Wed, 12 Mar 2008 14:48:00 -0000 [thread overview]
Message-ID: <20080312144656.GA4941@lucon.org> (raw)
In-Reply-To: <1205163133.6782.57.camel@otta>
On Mon, Mar 10, 2008 at 10:32:13AM -0500, Peter Bergner wrote:
> On Thu, 2008-02-28 at 17:08 -0600, Peter Bergner wrote:
> > HJ,
> >
> > Given the x86/x86_64 issues with the last indexed load/store patch,
> > can you SPEC test this patch to make sure the rtlanal.c change doesn't
> > affect you? Thanks.
>
> HJ,
>
> If you get a chance, can you please SPEC test the patch located in:
>
> http://gcc.gnu.org/ml/gcc-patches/2008-02/msg01442.html
>
> just to make sure it doesn't have a negative impact on x86/x86_64?
> Thanks.
Hi Peter,
I can use gcc to compile SPEC CPU now. But your patch won't apply
patching file rtlanal.c
patching file gcse.c
Hunk #2 succeeded at 4463 (offset 7 lines).
Hunk #4 succeeded at 6120 (offset 7 lines).
patching file emit-rtl.c
Reversed (or previously applied) patch detected! Assume -R? [n]
against revision 133140. Do you have an updated patch?
Thanks.
H.J.
next prev parent reply other threads:[~2008-03-12 14:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 22:30 Peter Bergner
2008-02-25 23:13 ` Peter Bergner
2008-02-26 5:25 ` [PATCH,updated] " Peter Bergner
2008-02-26 5:49 ` [PATCH,withdrawn] " Peter Bergner
2008-02-26 18:00 ` [PATCH] " Richard Sandiford
2008-02-26 19:04 ` Peter Bergner
2008-02-26 19:45 ` Richard Sandiford
2008-02-26 20:06 ` Jeff Law
2008-02-29 1:32 ` Peter Bergner
2008-03-03 19:17 ` Jeff Law
2008-03-03 19:42 ` Peter Bergner
2008-03-03 20:55 ` Jeff Law
2008-03-10 15:32 ` [PING H.J. Lu] " Peter Bergner
2008-03-10 16:22 ` H.J. Lu
2008-03-12 14:48 ` H.J. Lu [this message]
2008-03-17 14:32 ` H.J. Lu
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=20080312144656.GA4941@lucon.org \
--to=hjl.tools@gmail.com \
--cc=bergner@vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=rsandifo@nildram.co.uk \
/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).