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/56635] [4.8/4.9 regression] internal compiler error: in find_lattice_value, at tree-complex.c:15 Date: Wed, 20 Mar 2013 08:43:00 -0000 [thread overview] Message-ID: <bug-56635-4-aheMou6Bkv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56635-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56635 --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-03-20 08:42:52 UTC --- Author: jakub Date: Wed Mar 20 08:40:08 2013 New Revision: 196808 URL: http://gcc.gnu.org/viewcvs?rev=196808&root=gcc&view=rev Log: PR tree-optimization/56635 * tree-ssa-phiopt.c (cond_if_else_store_replacement_1): Give up if lhs of then_assign and else_assign don't have compatible types. * g++.dg/torture/pr56635.C: New test. Added: branches/gcc-4_8-branch/gcc/testsuite/g++.dg/torture/pr56635.C Modified: branches/gcc-4_8-branch/gcc/ChangeLog branches/gcc-4_8-branch/gcc/testsuite/ChangeLog branches/gcc-4_8-branch/gcc/tree-ssa-phiopt.c
prev parent reply other threads:[~2013-03-20 8:43 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-16 15:11 [Bug c/56635] New: [4.8 " orion at cora dot nwra.com 2013-03-16 16:20 ` [Bug c/56635] " jakub at gcc dot gnu.org 2013-03-17 1:44 ` orion at cora dot nwra.com 2013-03-17 4:45 ` markus at trippelsdorf dot de 2013-03-17 5:53 ` [Bug tree-optimization/56635] " pinskia at gcc dot gnu.org 2013-03-18 8:27 ` [Bug tree-optimization/56635] [4.8/4.9 " jakub at gcc dot gnu.org 2013-03-18 8:47 ` jakub at gcc dot gnu.org 2013-03-18 9:03 ` jakub at gcc dot gnu.org 2013-03-18 13:02 ` jakub at gcc dot gnu.org 2013-03-20 8:43 ` jakub at gcc dot gnu.org 2013-03-20 8:43 ` 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-56635-4-aheMou6Bkv@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).