public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/44061] [4.6/4.7/4.8 Regression] Warns about out-of-bounds array access inside __builtin_constant_p guarded section
Date: Fri, 11 Jan 2013 10:20:00 -0000	[thread overview]
Message-ID: <bug-44061-4-kYi68Qe6Yx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44061-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> 2013-01-11 10:20:13 UTC ---
Author: rguenth
Date: Fri Jan 11 10:20:02 2013
New Revision: 195103

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=195103
Log:
2012-01-11  Richard Guenther  <rguenther@suse.de>

    PR tree-optimization/44061
    * tree-vrp.c (extract_range_basic): Compute zero as
    value-range for __builtin_constant_p of function parameters.

    * gcc.dg/pr44061.c: New testcase.

Added:
    trunk/gcc/testsuite/gcc.dg/pr44061.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-vrp.c


  parent reply	other threads:[~2013-01-11 10:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-44061-4@http.gcc.gnu.org/bugzilla/>
2010-12-16 13:18 ` [Bug tree-optimization/44061] [4.5/4.6 " rguenth at gcc dot gnu.org
2011-04-28 15:39 ` [Bug tree-optimization/44061] [4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-07-02 12:05 ` [Bug tree-optimization/44061] [4.5/4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2012-12-11 10:36 ` [Bug tree-optimization/44061] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2013-01-10 15:36 ` rguenth at gcc dot gnu.org
2013-01-11 10:20 ` rguenth at gcc dot gnu.org [this message]
2013-01-11 10:21 ` [Bug tree-optimization/44061] [4.6/4.7 " rguenth at gcc dot gnu.org
2013-02-04 15:50 ` [Bug tree-optimization/44061] [4.6 " rguenth at gcc dot gnu.org
2013-02-04 15:50 ` [Bug tree-optimization/44061] [4.6/4.7 " rguenth 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-44061-4-kYi68Qe6Yx@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).