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/60861] out of bounds access of  global var in .rodata/.bss not detected
Date: Thu, 17 Apr 2014 09:13:00 -0000	[thread overview]
Message-ID: <bug-60861-4-L480PJfGbZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60861-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60861

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'd say it is fine for test to be optimized to 1 at -O2, but am not sure we
want to do that even for -O0 (and if we disable it for -O0, whether we want it
for -Og).  Then it will be user's choice whether he wants to instrument
optimized code (where there is no out of bound access), or non-optimized code
(where there would be out of bounds access).


      parent reply	other threads:[~2014-04-17  9:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 15:17 [Bug sanitizer/60861] New: " jan.smets@alcatel-lucent.com
2014-04-16 19:02 ` [Bug sanitizer/60861] " kcc at gcc dot gnu.org
2014-04-16 21:33 ` jan.smets@alcatel-lucent.com
2014-04-17  5:00 ` y.gribov at samsung dot com
2014-04-17  5:04 ` pinskia at gcc dot gnu.org
2014-04-17  6:32 ` y.gribov at samsung dot com
2014-04-17  8:30 ` kcc at gcc dot gnu.org
2014-04-17  9:13 ` jakub at gcc dot gnu.org [this message]

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-60861-4-L480PJfGbZ@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).