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 c/61184] [4.10 Regression] wrong code (that hangs) by LTO on x86_64-linux-gnu
Date: Mon, 19 May 2014 10:16:00 -0000 [thread overview]
Message-ID: <bug-61184-4-vzyphabzVb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61184-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61184
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Ok, it's rather an old bug in vrp_operand_equal_p which does
if (is_overflow_infinity (val1))
return is_overflow_infinity (val2);
which isn't correct for how it is called from update_value_range
(old value first, new value last and in this particular case
+INF and +INF(OVF) which are happily classified as equal).
next prev parent reply other threads:[~2014-05-19 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 1:30 [Bug lto/61184] New: " su at cs dot ucdavis.edu
2014-05-14 8:53 ` [Bug c/61184] [4.10 Regression] " rguenth at gcc dot gnu.org
2014-05-19 10:16 ` rguenth at gcc dot gnu.org [this message]
2014-05-19 12:32 ` rguenth at gcc dot gnu.org
2014-05-19 12:47 ` [Bug tree-optimization/61184] " rguenth at gcc dot gnu.org
2014-05-21 9:17 ` schwab@linux-m68k.org
2014-05-23 8:14 ` 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-61184-4-vzyphabzVb@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).