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/59410] Some tsan tests fail with 4GB RAM Date: Fri, 06 Dec 2013 16:37:00 -0000 [thread overview] Message-ID: <bug-59410-4-3msCzcP7bt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59410-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Have any attempt for saner tsan shadow memory mapping be done in the last year? I mean, there were some PRs or mailing list threads about it being worth to support also non-PIE executables etc., understandably it didn't happen for GCC 4.8, because there wasn't enough time for it, but do we have to live with that limitation forever?
next prev parent reply other threads:[~2013-12-06 16:37 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-06 16:28 [Bug sanitizer/59410] New: " hjl.tools at gmail dot com 2013-12-06 16:31 ` [Bug sanitizer/59410] " dvyukov at google dot com 2013-12-06 16:31 ` jakub at gcc dot gnu.org 2013-12-06 16:32 ` kcc at gcc dot gnu.org 2013-12-06 16:34 ` kcc at gcc dot gnu.org 2013-12-06 16:37 ` jakub at gcc dot gnu.org [this message] 2013-12-06 16:41 ` hjl.tools at gmail dot com 2013-12-06 16:42 ` hjl.tools at gmail dot com 2013-12-06 16:44 ` kcc at gcc dot gnu.org 2013-12-06 16:46 ` kcc at gcc dot gnu.org 2013-12-06 16:51 ` hjl.tools at gmail dot com 2013-12-06 16:56 ` kcc at gcc dot gnu.org 2013-12-06 16:56 ` hjl.tools at gmail dot com 2013-12-06 17:04 ` hjl.tools at gmail dot com 2013-12-06 17:05 ` jakub at gcc dot gnu.org 2013-12-06 17:11 ` kcc at gcc dot gnu.org 2013-12-06 17:15 ` kcc at gcc dot gnu.org 2013-12-06 17:23 ` hjl.tools at gmail dot com 2013-12-06 17:24 ` [Bug sanitizer/59410] tsan tests fail with address randomization disabled hjl.tools at gmail dot com 2013-12-06 17:26 ` hjl.tools at gmail dot com 2013-12-06 18:03 ` hjl.tools at gmail dot com 2013-12-06 18:08 ` kcc at gcc dot gnu.org 2013-12-06 18:16 ` hjl.tools at gmail dot com 2013-12-06 18:18 ` hjl.tools at gmail dot com 2013-12-07 8:02 ` kcc at gcc dot gnu.org 2013-12-07 11:26 ` hjl.tools at gmail dot com 2013-12-09 6:38 ` y.gribov at samsung dot com 2013-12-09 7:19 ` jakub at gcc dot gnu.org 2013-12-09 7:44 ` kcc at gcc dot gnu.org 2013-12-09 12:42 ` hjl.tools at gmail dot com 2014-01-31 12:27 ` y.gribov at samsung dot com 2014-01-31 21:26 ` jakub at gcc dot gnu.org 2014-12-12 16:17 ` dvyukov at google dot com 2014-12-12 16:46 ` hjl.tools at gmail dot com 2014-12-12 19:37 ` kcc at gcc dot gnu.org 2014-12-12 20:13 ` hjl.tools at gmail dot com 2014-12-23 4:43 ` dvyukov at google dot com 2014-12-23 4:45 ` dvyukov at google 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-59410-4-3msCzcP7bt@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).