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 tree-optimization/65875] [5/6 Regression] ICE: Segmentation fault Date: Mon, 27 Apr 2015 11:26:00 -0000 [thread overview] Message-ID: <bug-65875-4-d9MdUwUbkl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65875-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65875 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Author: jakub Date: Mon Apr 27 11:26:12 2015 New Revision: 222458 URL: https://gcc.gnu.org/viewcvs?rev=222458&root=gcc&view=rev Log: PR tree-optimization/65875 * tree-vrp.c (update_value_range): If in is_new case setting old_vr to VR_VARYING, also set new_vr to it. Remove old_vr->type == VR_VARYING test. (vrp_visit_phi_node): Return SSA_PROP_VARYING instead of SSA_PROP_INTERESTING if update_value_range returned true, but new range is VR_VARYING. * gcc.c-torture/compile/pr65875.c: New test. Added: trunk/gcc/testsuite/gcc.c-torture/compile/pr65875.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-vrp.c
next prev parent reply other threads:[~2015-04-27 11:26 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-24 12:16 [Bug c/65875] New: internal compiler error with gcc 5.1 megahallon at gmail dot com 2015-04-24 12:29 ` [Bug tree-optimization/65875] [5/6 Regression] ICE: Segmentation fault trippels at gcc dot gnu.org 2015-04-24 16:37 ` jakub at gcc dot gnu.org 2015-04-27 9:15 ` rguenth at gcc dot gnu.org 2015-04-27 11:26 ` jakub at gcc dot gnu.org [this message] 2015-04-27 12:21 ` jakub at gcc dot gnu.org 2015-04-27 12:29 ` jakub at gcc dot gnu.org 2015-04-28 7:51 ` jakub at gcc dot gnu.org 2015-04-28 8:16 ` rguenther at suse dot de 2015-04-28 8:28 ` jakub 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-65875-4-d9MdUwUbkl@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: linkBe 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).