public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/55439] ThreadSanitizer: handle atomic operations Date: Tue, 04 Dec 2012 13:21:00 -0000 [thread overview] Message-ID: <bug-55439-4-0L1DUWkZGG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55439-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55439 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-12-04 13:20:35 UTC --- Author: jakub Date: Tue Dec 4 13:20:20 2012 New Revision: 194133 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=194133 Log: PR sanitizer/55439 * Makefile.in (tsan.o): Depend on tree-ssa-propagate.h. * sanitizer.def: Add __tsan_atomic* builtins. * asan.c (initialize_sanitizer_builtins): Adjust to also initialize __tsan_atomic* builtins. * tsan.c: Include tree-ssa-propagate.h. (enum tsan_atomic_action): New enum. (tsan_atomic_table): New table. (instrument_builtin_call): New function. (instrument_gimple): Take pointer to gimple_stmt_iterator instead of gimple_stmt_iterator. Call instrument_builtin_call on builtin call stmts. (instrument_memory_accesses): Adjust instrument_gimple caller. * builtin-types.def (BT_FN_BOOL_VPTR_PTR_I1_INT_INT, BT_FN_BOOL_VPTR_PTR_I2_INT_INT, BT_FN_BOOL_VPTR_PTR_I4_INT_INT, BT_FN_BOOL_VPTR_PTR_I8_INT_INT, BT_FN_BOOL_VPTR_PTR_I16_INT_INT): New. Modified: trunk/gcc/ChangeLog trunk/gcc/Makefile.in trunk/gcc/asan.c trunk/gcc/builtin-types.def trunk/gcc/sanitizer.def trunk/gcc/tsan.c
next prev parent reply other threads:[~2012-12-04 13:21 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-22 7:42 [Bug other/55439] New: " dvyukov at google dot com 2012-11-22 7:55 ` [Bug other/55439] " dvyukov at google dot com 2012-12-04 13:21 ` jakub at gcc dot gnu.org [this message] 2013-11-19 10:29 ` [Bug sanitizer/55439] " Joost.VandeVondele at mat dot ethz.ch 2013-11-19 10:31 ` jakub 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-55439-4-0L1DUWkZGG@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).