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/50677] volatile forces load into register
Date: Sun, 09 Oct 2011 17:36:00 -0000 [thread overview]
Message-ID: <bug-50677-4-XqK5UOvV9S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50677-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50677
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011-10-09
Ever Confirmed|0 |1
--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-10-09 17:36:30 UTC ---
Well, the issue is that most optimization passes just don't do anything
for volatile qualified accesses. That's a safe thing. Deciding what
kind of optimizations are allowed for volatile accesses might introduce bugs,
and sofar the consensus was "volatile? don't bother with optimization, it'll
be slow anyway".
It very likely is combine that gives up here.
next prev parent reply other threads:[~2011-10-09 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 12:52 [Bug rtl-optimization/50677] New: " marc.glisse at normalesup dot org
2011-10-09 17:36 ` rguenth at gcc dot gnu.org [this message]
2011-10-09 19:49 ` [Bug rtl-optimization/50677] " pinskia at gcc dot gnu.org
2014-02-24 16:03 ` hjl.tools at gmail dot com
2014-02-24 16:17 ` pinskia at gcc dot gnu.org
2015-07-15 16:37 ` hjl.tools at gmail dot com
2015-07-15 17:07 ` hjl.tools at gmail dot com
2021-11-29 3:17 ` pinskia at gcc dot gnu.org
2022-09-27 23:37 ` pinskia at gcc dot gnu.org
2023-02-09 18:11 ` pinskia 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-50677-4-XqK5UOvV9S@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).