This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/16721] [3.5 Regression] Accesses to volatile objects optimized away
- From: "falk at debian dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Jul 2004 19:30:15 -0000
- Subject: [Bug c/16721] [3.5 Regression] Accesses to volatile objects optimized away
- References: <20040726181156.16721.macro@linux-mips.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From falk at debian dot org 2004-07-26 19:30 -------
I don't think that's what the standard says. Even if it did, it is not
what people expect. Read accesses can have effects on magic hardware
addresses, and you need volatile to keep the compiler from optimizing
these away.
So I still think this is an important bug.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16721