public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zeccav at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67279] -fsanitize=undefined spurious error: initializer element is not constant
Date: Wed, 19 Aug 2015 19:33:00 -0000	[thread overview]
Message-ID: <bug-67279-4-LajnmEVgtT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67279-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67279

--- Comment #3 from Vittorio Zecca <zeccav at gmail dot com> ---
The following code has UB at lines 4 and 5 but compiles with
-fsanitize=undefined
int main()
{
int test[1],t;
t=test[1];
return test[1];
}

Its execution it delivers four runtime errors from the sanitizer and I
am happy with that
ps.c:4:7: runtime error: index 1 out of bounds for type 'int [1]'
ps.c:4:2: runtime error: load of address 0x7ffcb21195f4 with
insufficient space for an object of type 'int'
0x7ffcb21195f4: note: pointer points here
  e0 96 11 b2 fc 7f 00 00  00 00 00 00 00 00 00 00  70 07 40 00 00 00
00 00  e0 ff a1 0d 39 00 00 00
              ^
ps.c:5:12: runtime error: index 1 out of bounds for type 'int [1]'
ps.c:5:8: runtime error: load of address 0x7ffcb21195f4 with
insufficient space for an object of type 'int'
0x7ffcb21195f4: note: pointer points here
  e0 96 11 b2 fc 7f 00 00  00 00 00 00 fc 7f 00 00  70 07 40 00 00 00
00 00  e0 ff a1 0d 39 00 00 00

In short: I like to see gcc -fsanitize=undefined to compile codes it
compiles without sanitation


  parent reply	other threads:[~2015-08-19 19:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 17:06 [Bug c/67279] New: " zeccav at gmail dot com
2015-08-19 17:09 ` [Bug c/67279] " mpolacek at gcc dot gnu.org
2015-08-19 18:59 ` zeccav at gmail dot com
2015-08-19 19:33 ` zeccav at gmail dot com [this message]
2015-08-19 19:55 ` manu at gcc dot gnu.org
2015-08-20  7:15 ` zeccav at gmail dot com
2015-08-20  8:38 ` mpolacek at gcc dot gnu.org
2015-09-02 21:01 ` mpolacek at gcc dot gnu.org
2015-09-04 12:38 ` mpolacek 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-67279-4-LajnmEVgtT@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).