public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "muecker at gwdg dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/104800] reodering of potentially trapping operations and volatile stores
Date: Wed, 09 Mar 2022 07:42:57 +0000 [thread overview]
Message-ID: <bug-104800-4-6i2Csg0NGs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104800-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104800
--- Comment #12 from Martin Uecker <muecker at gwdg dot de> ---
(In reply to Richard Biener from comment #10)
> Btw, with -ftrapv it would mean we cannot re-order any signed arithmetic
> with respect to volatile accesses unless we can prove it does not invoke
> (undefined,
> but -ftrapv makes it implementation defined) signed overflow.
Yes, and I think this would be desirable too. For example, if you safetly turn
off a machine with a volatile store, you want a later logic error in unrelated
code not to be able to prevent this.
next prev parent reply other threads:[~2022-03-09 7:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 18:46 [Bug tree-optimization/104800] New: " muecker at gwdg dot de
2022-03-05 18:50 ` [Bug tree-optimization/104800] " muecker at gwdg dot de
2022-03-05 21:07 ` pinskia at gcc dot gnu.org
2022-03-06 5:04 ` [Bug middle-end/104800] " paulmckrcu at gmail dot com
2022-03-06 6:46 ` muecker at gwdg dot de
2022-03-06 6:54 ` muecker at gwdg dot de
2022-03-07 8:52 ` rguenth at gcc dot gnu.org
2022-03-07 17:47 ` paulmckrcu at gmail dot com
2022-03-08 20:27 ` muecker at gwdg dot de
2022-03-09 7:26 ` rguenth at gcc dot gnu.org
2022-03-09 7:29 ` rguenth at gcc dot gnu.org
2022-03-09 7:40 ` muecker at gwdg dot de
2022-03-09 7:42 ` muecker at gwdg dot de [this message]
2022-03-09 7:52 ` rguenther at suse dot de
2022-03-09 8:06 ` rguenther at suse dot de
2022-03-09 9:05 ` muecker at gwdg dot de
2022-03-09 9:10 ` muecker at gwdg dot de
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-104800-4-6i2Csg0NGs@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).