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 middle-end/60121] gcc does not warn an obvious out-of-bound array access at -O0 and -O1
Date: Sun, 09 Feb 2014 06:39:00 -0000	[thread overview]
Message-ID: <bug-60121-4-gJGFpCsQml@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60121-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
No.  VRP isn't really a cheap pass and for -O0 the most important thing is
compile time speed.  GCC has never guaranteed the same warnings between
optimization levels, for frontend warnings it is sometimes possible to have the
same warnings, but for middle-end warnings it is not possible and never a goal.
Think say about uninitialized warnings, some of them heavily depend on which
functions are inlined and which are not.


      parent reply	other threads:[~2014-02-09  6:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 23:15 [Bug c/60121] New: " su at cs dot ucdavis.edu
2014-02-08 23:41 ` [Bug middle-end/60121] " pinskia at gcc dot gnu.org
2014-02-09  0:08 ` su at cs dot ucdavis.edu
2014-02-09  0:14 ` pinskia at gcc dot gnu.org
2014-02-09  0:18 ` su at cs dot ucdavis.edu
2014-02-09  0:32 ` chengniansun at gmail dot com
2014-02-09  0:47 ` pinskia at gcc dot gnu.org
2014-02-09  1:27 ` chengniansun at gmail dot com
2014-02-09  6:39 ` 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-60121-4-gJGFpCsQml@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).