public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/51374] [avr] insn combine reorders volatile memory accesses
Date: Wed, 01 Feb 2012 12:47:00 -0000	[thread overview]
Message-ID: <bug-51374-4-xBnLyqA9jZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51374-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51374

--- Comment #11 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2012-02-01 12:46:42 UTC ---
Author: gjl
Date: Wed Feb  1 12:46:39 2012
New Revision: 183798

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183798
Log:
    PR rtl-optimization/51374
    * gcc.target/avr/torture/pr51374-1.c:
    Also fail if SBIS is seen.


Modified:
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gcc.target/avr/torture/pr51374-1.c


  parent reply	other threads:[~2012-02-01 12:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01  5:01 [Bug c/51374] New: Volatile access reordered andyw at pobox dot com
2011-12-01  9:58 ` [Bug rtl-optimization/51374] [avr] insn combine reorders volatile memory accesses gjl at gcc dot gnu.org
2011-12-01  9:59 ` gjl at gcc dot gnu.org
2011-12-01 10:08 ` gjl at gcc dot gnu.org
2011-12-01 13:23 ` andyw at pobox dot com
2011-12-08 16:48 ` gjl at gcc dot gnu.org
2011-12-18 20:11 ` gjl at gcc dot gnu.org
2012-01-13 16:00 ` gjl at gcc dot gnu.org
2012-01-13 16:18 ` gjl at gcc dot gnu.org
2012-02-01 11:36 ` gjl at gcc dot gnu.org
2012-02-01 12:41 ` gjl at gcc dot gnu.org
2012-02-01 12:47 ` gjl at gcc dot gnu.org [this message]
2012-02-01 12:57 ` gjl at gcc dot gnu.org

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=bug-51374-4-xBnLyqA9jZ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).