public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/16721] [3.5 Regression] Accesses to volatile objects optimized away
Date: Mon, 26 Jul 2004 19:30:00 -0000 [thread overview]
Message-ID: <20040726193015.23570.qmail@sourceware.org> (raw)
In-Reply-To: <20040726181156.16721.macro@linux-mips.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
next prev parent reply other threads:[~2004-07-26 19:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 18:12 [Bug c/16721] New: Accesses to volatile objects optimized away with -fno-strict-aliasing gcc-bugzilla at gcc dot gnu dot org
2004-07-26 19:04 ` [Bug c/16721] [3.5 Regression] Accesses to volatile objects optimized away falk at debian dot org
2004-07-26 19:24 ` pinskia at gcc dot gnu dot org
2004-07-26 19:30 ` falk at debian dot org [this message]
2004-07-27 12:25 ` macro at linux-mips dot org
2004-07-27 12:50 ` macro at linux-mips dot org
2004-07-27 14:48 ` falk at debian dot org
2004-07-29 2:33 ` [Bug tree-optimization/16721] " pinskia at gcc dot gnu dot org
2004-07-29 11:27 ` macro at linux-mips dot org
2004-08-03 5:58 ` pinskia at gcc dot gnu dot org
2004-09-19 13:57 ` [Bug tree-optimization/16721] [4.0 " steven at gcc dot gnu dot org
2004-09-19 15:42 ` bangerth at dealii dot org
2004-09-22 14:41 ` dnovillo at gcc dot gnu dot org
2004-09-22 16:14 ` dnovillo at gcc dot gnu dot org
2004-09-22 16:26 ` stevenb at suse dot de
2004-09-22 16:41 ` dnovillo at redhat dot com
2004-09-22 17:23 ` dnovillo at gcc dot gnu dot org
2004-09-22 17:23 ` dnovillo at gcc dot gnu dot org
2004-09-22 23:33 ` cvs-commit at gcc dot gnu dot org
2004-09-22 23:36 ` dnovillo 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=20040726193015.23570.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).