public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tavianator at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/71613] Useful warnings silenced when macros from system headers are used
Date: Wed, 15 May 2024 14:49:22 +0000 [thread overview]
Message-ID: <bug-71613-4-uoKehmP1es@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-71613-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
Tavian Barnes <tavianator at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tavianator at gmail dot com
--- Comment #11 from Tavian Barnes <tavianator at gmail dot com> ---
Mostly commenting to make this searchable in case someone else runs into it:
-Wtsan is also affected by this:
$ cat foo.c
#include <stdatomic.h>
int main(void) {
atomic_thread_fence(memory_order_relaxed);
__atomic_thread_fence(__ATOMIC_RELAXED);
return 0;
}
$ gcc -c -fsanitize=thread foo.c
foo.c: In function ‘main’:
foo.c:5:9: warning: ‘atomic_thread_fence’ is not supported with
‘-fsanitize=thread’ [-Wtsan]
5 | __atomic_thread_fence(__ATOMIC_RELAXED);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
parent reply other threads:[~2024-05-15 14:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-71613-4@http.gcc.gnu.org/bugzilla/>]
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-71613-4-uoKehmP1es@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).