public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenther at suse 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 08:06:44 +0000 [thread overview] Message-ID: <bug-104800-4-LaXnOA5mRv@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 #14 from rguenther at suse dot de <rguenther at suse dot de> --- On Wed, 9 Mar 2022, muecker at gwdg dot de wrote: > 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. As said, volatile accesses are not considered to alter control flow and thus "turning off the machine" is not something GCC "allows", the program has to resume after the volatile store. For example volatile accesses are also not considered to abnormally return. Consider them raising an interrupt, that triggering a signal and using siglongjmp - GCC is not prepared for that to happen (so it's not "allowed"). The following might be eventually a catch-all fix (but too aggressive as noted in the comment). With it GCC should consider (on the GIMPLE / GENERIC level ...) all volatile accesses possibly trapping and thus altering control flow. diff --git a/gcc/tree-eh.cc b/gcc/tree-eh.cc index c37a5845343..21179081be9 100644 --- a/gcc/tree-eh.cc +++ b/gcc/tree-eh.cc @@ -2662,8 +2662,15 @@ tree_could_trap_p (tree expr) return false; code = TREE_CODE (expr); - t = TREE_TYPE (expr); + /* Volatile accesses need to be considered as altering control flow + if they are for example device I/O. + ??? We can probably exclude automatic variables and accesses that + are known to not map to device memory here. */ + if (TREE_CODE_CLASS (code) == tcc_reference + && TREE_THIS_VOLATILE (expr)) + return true; + t = TREE_TYPE (expr); if (t) { if (COMPARISON_CLASS_P (expr))
next prev parent reply other threads:[~2022-03-09 8:06 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 2022-03-09 7:52 ` rguenther at suse dot de 2022-03-09 8:06 ` rguenther at suse dot de [this message] 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-LaXnOA5mRv@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: linkBe 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).