public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dvyukov at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/64265] [5 Regression] r217669 broke tsan
Date: Fri, 12 Dec 2014 18:48:00 -0000 [thread overview]
Message-ID: <bug-64265-4-T50Y8w0rTt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64265-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64265
--- Comment #13 from Dmitry Vyukov <dvyukov at google dot com> ---
> ... we actually don't want any __tsan_func_{entry,exit} calls if there are no memory accesses in the function...
... and no calls to other functions, because these functions can contain memory
accesses and tsan needs func_entry/exit to maintain stack traces.
next prev parent reply other threads:[~2014-12-12 18:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 11:47 [Bug c++/64265] New: " bernd.edlinger at hotmail dot de
2014-12-12 13:31 ` [Bug c++/64265] " bernd.edlinger at hotmail dot de
2014-12-12 13:33 ` [Bug sanitizer/64265] [5 Regression] " rguenth at gcc dot gnu.org
2014-12-12 13:36 ` rguenth at gcc dot gnu.org
2014-12-12 13:39 ` bernd.edlinger at hotmail dot de
2014-12-12 15:58 ` edlinger at gcc dot gnu.org
2014-12-12 16:51 ` jakub at gcc dot gnu.org
2014-12-12 17:22 ` jakub at gcc dot gnu.org
2014-12-12 17:28 ` dvyukov at google dot com
2014-12-12 17:39 ` jakub at gcc dot gnu.org
2014-12-12 17:42 ` jakub at gcc dot gnu.org
2014-12-12 17:52 ` dvyukov at google dot com
2014-12-12 18:41 ` jakub at gcc dot gnu.org
2014-12-12 18:48 ` dvyukov at google dot com [this message]
2014-12-12 18:58 ` bernd.edlinger at hotmail dot de
2014-12-12 19:13 ` jakub at gcc dot gnu.org
2014-12-12 19:22 ` kcc at gcc dot gnu.org
2014-12-12 19:31 ` dvyukov at google dot com
2014-12-12 19:36 ` bernd.edlinger at hotmail dot de
2014-12-12 20:18 ` bernd.edlinger at hotmail dot de
2014-12-12 20:26 ` dvyukov at google dot com
2014-12-12 21:23 ` jakub at gcc dot gnu.org
2014-12-15 9:38 ` jakub at gcc dot gnu.org
2014-12-15 9:46 ` jakub at gcc dot gnu.org
2014-12-15 9:50 ` jakub at gcc dot gnu.org
2014-12-16 12:04 ` jakub at gcc dot gnu.org
2015-01-05 21:48 ` jakub at gcc dot gnu.org
2015-03-19 7:55 ` 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-64265-4-T50Y8w0rTt@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).