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 target/54083] FAIL: gcc.dg/torture/pr53922.c on *-apple-darwin*
Date: Tue, 04 Sep 2012 11:10:00 -0000	[thread overview]
Message-ID: <bug-54083-4-ysXaG0euvY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54083-4@http.gcc.gnu.org/bugzilla/>

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-09-04
     Ever Confirmed|0                           |1

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-09-04 11:10:11 UTC ---
The failing test has been introduced by

Author: rguenth
Date: Fri Jul 13 11:21:39 2012
New Revision: 189461

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

    PR tree-optimization/53922
    * tree-vrp.c (value_inside_range): Change prototype to take
    min/max instead of value-range.
    (range_includes_zero_p): Likewise.  Return the result from
    value_inside_range.
    (extract_range_from_binary_expr_1): Adjust to handle dont-know
    return value from range_includes_zero_p.
    (extract_range_from_unary_expr_1): Likewise.
    (compare_range_with_value): Likewise.
    (vrp_meet_1): Likewise.

    * gcc.dg/torture/pr53922.c: New testcase.

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


  parent reply	other threads:[~2012-09-04 11:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 12:59 [Bug target/54083] New: FAIL: gcc.dg/torture/pr53922.c on x86_64-apple-darwin10 dominiq at lps dot ens.fr
2012-07-24 22:43 ` [Bug target/54083] FAIL: gcc.dg/torture/pr53922.c on *-apple-darwin* dominiq at lps dot ens.fr
2012-09-04 11:10 ` dominiq at lps dot ens.fr [this message]
2012-09-16 15:46 ` danglin at gcc dot gnu.org
2012-09-23 21:36 ` dominiq at lps dot ens.fr
2012-09-23 21:37 ` dominiq at lps dot ens.fr
2012-09-27 21:29 ` fang at csl dot cornell.edu
2012-09-27 21:33 ` dominiq at lps dot ens.fr
2012-09-30 17:42 ` danglin at gcc dot gnu.org
2012-09-30 17:44 ` danglin at gcc dot gnu.org
2012-09-30 17:55 ` danglin at gcc dot gnu.org
2012-11-19 16:49 ` dominiq at lps dot ens.fr
2012-11-19 17:01 ` howarth at nitro dot med.uc.edu
2012-11-19 21:34 ` iains at gcc dot gnu.org
2012-11-19 21:41 ` fang at csl dot cornell.edu
2012-11-19 21:54 ` iains at gcc dot gnu.org
2013-03-11 18:23 ` dominiq at lps dot ens.fr
2014-03-26 22:11 ` dominiq at lps dot ens.fr
2014-03-26 22:43 ` dave.anglin at bell dot net
2014-03-26 23:29 ` dominiq at lps dot ens.fr
2014-03-27  0:17 ` dave.anglin at bell dot net
2014-03-27  9:37 ` dominiq at lps dot ens.fr
2014-04-02  8:58 ` dominiq at gcc dot gnu.org
2014-04-06 11:44 ` dominiq at gcc dot gnu.org
2014-04-06 11:45 ` dominiq at lps dot ens.fr

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-54083-4-ysXaG0euvY@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).