public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rogero at howzatt dot demon.co.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/63559] New: -fsanitize=thread sets no preprocessor flags Date: Thu, 16 Oct 2014 11:34:00 -0000 [thread overview] Message-ID: <bug-63559-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63559 Bug ID: 63559 Summary: -fsanitize=thread sets no preprocessor flags Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: rogero at howzatt dot demon.co.uk CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org When -fsanitize=address is supplied the builtin __SANITIZE_ADDRESS__ is defined. There does not appear to be an equivalent for -fsanitize=thread, which could be used for conditionally compiling code to avoid tsan reporting false positives.
next reply other threads:[~2014-10-16 11:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-16 11:34 rogero at howzatt dot demon.co.uk [this message] 2014-10-16 12:01 ` [Bug sanitizer/63559] " dvyukov at google dot com 2014-10-16 19:58 ` rogero at howzatt dot demon.co.uk 2014-10-17 3:36 ` dvyukov at google dot com 2023-12-17 3:58 ` pinskia at gcc dot gnu.org
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-63559-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).