From: Richard Guenther <rguenther@suse.de>
To: Richard Henderson <rth@redhat.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
Eric Botcazou <ebotcazou@adacore.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 3/3] rs6000: Rewrite sync patterns for atomic; expand early.
Date: Wed, 13 Jun 2012 08:47:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1206131033130.29541@jbgna.fhfr.qr> (raw)
In-Reply-To: <4FD76567.2070506@redhat.com>
On Tue, 12 Jun 2012, Richard Henderson wrote:
> On 2012-06-11 18:40, David Edelsohn wrote:
> >> > Nope. I do see the obvious mistake in the atomic_load pattern though:
> >> > The mode iterator should have been INT1 not INT.
> > Did you want to commit the fix for the iterator?
> >
>
> Applied the following to mainline.
>
> It ought to go onto the 4.7 branch as well, as it's a wrong-code bug.
> Are we at a place in the 4.7.1 release process where that's possible?
If you are sure it won't break anything go ahead (sooner than later
please).
Thanks,
Richard.
next prev parent reply other threads:[~2012-06-13 8:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 11:07 [PATCH 0/3] Conversion to __atomic builtins Richard Henderson
2011-11-12 11:45 ` [PATCH 2/3] ppc-linux: Fix call to _Unwind_SetGRPtr Richard Henderson
2011-11-12 13:23 ` [PATCH 3/3] rs6000: Rewrite sync patterns for atomic; expand early Richard Henderson
2011-11-14 21:57 ` David Edelsohn
2012-06-09 12:47 ` Eric Botcazou
2012-06-09 16:40 ` Richard Henderson
2012-06-12 2:30 ` David Edelsohn
2012-06-12 13:56 ` Richard Henderson
2012-06-12 17:46 ` Mike Stump
2012-06-12 23:47 ` David Edelsohn
2012-06-13 15:27 ` Richard Henderson
2012-06-12 15:58 ` Richard Henderson
2012-06-12 23:16 ` David Edelsohn
2012-06-13 8:47 ` Richard Guenther [this message]
2012-06-13 15:41 ` Richard Henderson
2011-11-12 13:47 ` [PATCH 1/3] rs6000: fix*_trunc insns use nonimmediate_operand Richard Henderson
2011-11-12 15:59 ` [PATCH 0/3] Conversion to __atomic builtins David Edelsohn
2011-11-14 22:43 ` David Edelsohn
2011-11-15 6:01 ` Richard Henderson
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.1206131033130.29541@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=dje.gcc@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@redhat.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).