public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/22000] [4.0 Regression] Read from volatile member of struct is optimized away
Date: Fri, 10 Jun 2005 14:07:00 -0000	[thread overview]
Message-ID: <20050610140744.20371.qmail@sourceware.org> (raw)
In-Reply-To: <20050610135925.22000.rpedersen@atmel.com>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-06-10 14:07 -------
This works on the mainline, it might work on the 4.0.x branch too but I did not check yet.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|critical                    |normal
  GCC build triplet|i686-pc-linux-gnu           |
   GCC host triplet|i686-pc-linux-gnu           |
 GCC target triplet|arm-unknown-elf             |
           Keywords|                            |wrong-code
      Known to fail|                            |4.0.0
      Known to work|                            |4.1.0 3.4.0
            Summary|Read from volatile member of|[4.0 Regression] Read from
                   |struct is optimized away    |volatile member of struct is
                   |                            |optimized away


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


  parent reply	other threads:[~2005-06-10 14:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10 13:59 [Bug tree-optimization/22000] New: " rpedersen at atmel dot com
2005-06-10 14:00 ` [Bug tree-optimization/22000] " rpedersen at atmel dot com
2005-06-10 14:07 ` pinskia at gcc dot gnu dot org [this message]
2005-06-10 14:16 ` [Bug tree-optimization/22000] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-06-13  6:42 ` rpedersen at atmel dot com
2005-06-13 11:17 ` schlie at comcast dot net
2005-06-13 11:56 ` rpedersen at atmel dot com
2005-06-13 14:12 ` schlie at comcast dot net
2005-06-23 14:42 ` [Bug tree-optimization/22000] [4.0/4.1 " pinskia at gcc dot gnu dot org
2005-06-23 15:11 ` mmitchel at gcc dot gnu dot org
2005-06-23 15:28 ` mmitchel at gcc dot gnu dot org
2005-06-23 16:59 ` joseph at codesourcery dot com
2005-06-23 20:15 ` cvs-commit at gcc dot gnu dot org
2005-06-23 20:23 ` [Bug tree-optimization/22000] [4.1 " mmitchel at gcc dot gnu dot org
2005-06-24  3:38 ` cvs-commit at gcc dot gnu dot org
2005-06-24  3:40 ` mmitchel at gcc dot gnu dot 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=20050610140744.20371.qmail@sourceware.org \
    --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).