public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tilps at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98632] New: Warn about unspecified expression ordering for atomics with non-relaxed memory ordering. Date: Tue, 12 Jan 2021 10:13:58 +0000 [thread overview] Message-ID: <bug-98632-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98632 Bug ID: 98632 Summary: Warn about unspecified expression ordering for atomics with non-relaxed memory ordering. Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: tilps at hotmail dot com Target Milestone: --- C++ defines that execution ordering for expressions is largely unspecified. In cases where there are multiple atomic operations in an expression for which there is no standard required ordering, and if those atomic operations are marked with a non-relaxed memory ordering, it would be useful to have a warning. Since the compiler is technically free to reorder them in-spite of the memory ordering indicating that the user cares about the specific ordering. While it might be able to be argued that the warning should fire for any expression involving just a single atomic and some other expression component that would be unable to be reordered if the sub-expressions had been assigned to locals first, it seems that would be likely to have vastly more false positives than expressions that involve multiple atomic operations. So I would suggest only triggering for expressions involving multiple atomic operations.
next reply other threads:[~2021-01-12 10:13 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-12 10:13 tilps at hotmail dot com [this message] 2021-01-12 15:46 ` [Bug c++/98632] " redi at gcc dot gnu.org 2021-01-13 13:18 ` tilps at hotmail dot com
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-98632-4@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).