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 tree-optimization/105030] store motion if-change flag causes if-conversion optimization can't be taken.
Date: Wed, 23 Mar 2022 10:52:56 +0000 [thread overview]
Message-ID: <bug-105030-4-eGWXpXFdWh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105030-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105030
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
That occured to me as well - I think the answer is maybe. In principle
foo() could launch a thread and make the 'atemp' available to it. As long
as foo() outlives thread termination that should be all well-defined and so
we'd have to take this possibility into account.
There's currently no code ruling this out and doing that is likely difficult.
So maybe the answer is to add -fallow-store-data-races={local,all}, map
-fallow-store-data-races to -fallow-store-data-races=all and make
-fallow-store-data-races=local the default?
next prev parent reply other threads:[~2022-03-23 10:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 1:29 [Bug tree-optimization/105030] New: " guihaoc at gcc dot gnu.org
2022-03-23 6:21 ` [Bug tree-optimization/105030] " guihaoc at gcc dot gnu.org
2022-03-23 10:52 ` rguenth at gcc dot gnu.org [this message]
2022-03-24 3:05 ` guihaoc at gcc dot gnu.org
2022-03-24 7:22 ` rguenth at gcc dot gnu.org
2022-03-25 6:34 ` guihaoc at gcc dot gnu.org
2022-03-25 7:04 ` rguenther at suse dot de
2022-03-25 7:41 ` guihaoc at gcc dot gnu.org
2022-03-25 8:16 ` rguenther at suse dot de
2022-03-28 9:35 ` guihaoc at gcc dot gnu.org
2022-03-28 9:56 ` rguenther at suse dot de
2022-04-08 6:31 ` guihaoc at gcc dot gnu.org
2022-04-08 7:06 ` rguenth at gcc dot gnu.org
2022-04-08 7:53 ` guihaoc at gcc dot gnu.org
2022-04-08 8:07 ` rguenther at suse 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-105030-4-eGWXpXFdWh@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).