public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/55679] new asan tests from r194458 fail on x86_64-apple-darwin10
Date: Sun, 16 Dec 2012 18:23:00 -0000 [thread overview]
Message-ID: <bug-55679-4-CjWsUmXbfy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55679-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55679
--- Comment #16 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-12-16 18:23:24 UTC ---
(In reply to comments #12 and #13)
With -O1, the invalid tests c-c++-common/asan/global-overflow-1.c and
c-c++-common/asan/stack-overflow-1.c are optimized to a valid "return 0" as
shown by the following differences between the outputs of -dump-tree-optimized
with and without -fno-tree-fre:
--- stack-overflow-1.c.164t.optimized 2012-12-16 17:26:13.000000000 +0100
+++ stack-overflow-1.c.164t_f.optimized 2012-12-16 17:25:13.000000000 +0100
@@ -3,18 +3,14 @@
main ()
{
- int res;
char x[10];
int ten.1;
- char _4;
<bb 2>:
__builtin_memset (&x, 0, 10);
ten.1_3 ={v} ten;
- _4 = x[ten.1_3];
- res_5 = (int) _4;
x ={v} {CLOBBER};
- return res_5;
+ return 0;
}
So the problem for these two tests has nothing to do with asan. Note that they
regress cleanly if I add '-fno-tree-fre -fno-tree-pre' to '-fno-builtin-memset'
in the dg-options. The optimization is also defeated If I add a line such as
x[1] = 1;
Although I doubt this behavior is a bug, I'll open a new PR for it tomorrow
unless there is some objection.
next prev parent reply other threads:[~2012-12-16 18:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 22:14 [Bug sanitizer/55679] New: " howarth at nitro dot med.uc.edu
2012-12-13 22:16 ` [Bug sanitizer/55679] " howarth at nitro dot med.uc.edu
2012-12-13 22:21 ` howarth at nitro dot med.uc.edu
2012-12-14 0:07 ` howarth at nitro dot med.uc.edu
2012-12-14 0:13 ` howarth at nitro dot med.uc.edu
2012-12-14 0:18 ` howarth at nitro dot med.uc.edu
2012-12-14 0:21 ` howarth at nitro dot med.uc.edu
2012-12-14 0:23 ` howarth at nitro dot med.uc.edu
2012-12-14 0:37 ` howarth at nitro dot med.uc.edu
2012-12-14 0:45 ` howarth at nitro dot med.uc.edu
2012-12-14 1:23 ` howarth at nitro dot med.uc.edu
2012-12-14 7:22 ` dominiq at lps dot ens.fr
2012-12-14 16:24 ` dominiq at lps dot ens.fr
2012-12-14 21:25 ` howarth at nitro dot med.uc.edu
2012-12-14 23:32 ` dominiq at lps dot ens.fr
2012-12-15 3:09 ` howarth at nitro dot med.uc.edu
2012-12-16 18:23 ` dominiq at lps dot ens.fr [this message]
2012-12-16 21:41 ` dominiq at lps dot ens.fr
2012-12-18 15:15 ` howarth at nitro dot med.uc.edu
2013-01-17 21:29 ` mrs at gcc dot gnu.org
2013-01-20 16:55 ` dominiq at lps dot ens.fr
2013-01-23 17:34 ` 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-55679-4-CjWsUmXbfy@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).