public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/55577] g++.dg/asan/asan_test.C failures
Date: Mon, 03 Dec 2012 18:48:00 -0000 [thread overview]
Message-ID: <bug-55577-4-TxknSNJecm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55577-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55577
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-12-03 18:48:08 UTC ---
> Everybody has them, I've said in the mail containing the patch that there are a
> few unanalyzed failures, and what the reasons for some of those failures are
> (e.g. not instrumenting bitfields yet).
Ah, sorry. You can XFAIL them in the meantime though, adding testcases that
don't pass is a bit weird in my opinion.
next prev parent reply other threads:[~2012-12-03 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 17:43 [Bug sanitizer/55577] New: " hjl.tools at gmail dot com
2012-12-03 17:59 ` [Bug sanitizer/55577] " ebotcazou at gcc dot gnu.org
2012-12-03 18:44 ` jakub at gcc dot gnu.org
2012-12-03 18:48 ` ebotcazou at gcc dot gnu.org [this message]
2014-08-28 14:44 ` hjl.tools at gmail 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-55577-4-TxknSNJecm@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).