public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/55938] g++.dg/asan/deep-stack-uaf-1.C fails at r195092 on darwin
Date: Wed, 16 Jan 2013 01:18:00 -0000 [thread overview]
Message-ID: <bug-55938-4-RsWLzEwPBb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55938-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55938
--- Comment #4 from Jack Howarth <howarth at nitro dot med.uc.edu> 2013-01-16 01:18:08 UTC ---
(In reply to comment #3)
> > Failure no longer present at r195150 remerged with llvm compiler-rt r172419 .
>
> Could you post the corresponding fix?
I haven't bothered trying to regression hunt llvm compiler-rt since the changes
are always merged in bulk back from llvm. We'll have to wait until kcc does the
next merge to grab the fix.
next prev parent reply other threads:[~2013-01-16 1:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 2:18 [Bug sanitizer/55938] New: " howarth at nitro dot med.uc.edu
2013-01-11 6:37 ` [Bug sanitizer/55938] " kcc at gcc dot gnu.org
2013-01-14 15:33 ` howarth at nitro dot med.uc.edu
2013-01-15 16:55 ` dominiq at lps dot ens.fr
2013-01-16 1:18 ` howarth at nitro dot med.uc.edu [this message]
2013-02-16 2:04 ` howarth at nitro dot med.uc.edu
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-55938-4-RsWLzEwPBb@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).