public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/45852] volatile structs are broken!
Date: Fri, 01 Oct 2010 10:27:00 -0000	[thread overview]
Message-ID: <20101001102700.qS2L1YQ_vcW9J5qidcanzQYMPtrSD2jhNNOa2xYJ4aA@z> (raw)
In-Reply-To: <bug-45852-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-code
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2010.10.01 10:27:24
          Component|c                           |rtl-optimization
     Ever Confirmed|0                           |1

--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-10-01 10:27:24 UTC ---
The expander throws away the assignment.


  parent reply	other threads:[~2010-10-01 10:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01  3:10 [Bug c/45852] New: " regehr at cs dot utah.edu
2010-10-01  3:40 ` [Bug c/45852] " regehr at cs dot utah.edu
2010-10-01 10:27 ` rguenth at gcc dot gnu.org [this message]
2010-12-14 13:44 ` [Bug middle-end/45852] " jakub at gcc dot gnu.org
2010-12-14 14:55 ` amonakov at gcc dot gnu.org
2010-12-21  8:35 ` jakub at gcc dot gnu.org
2011-01-16 20:27 ` jakub at gcc dot gnu.org
2011-01-17  0:37 ` jakub at gcc dot gnu.org
2011-01-17  8:05 ` jakub 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=20101001102700.qS2L1YQ_vcW9J5qidcanzQYMPtrSD2jhNNOa2xYJ4aA@z \
    --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).