public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "christophe.lyon at st dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/61430] [4.10 regression] ICE in lra_create_copy Date: Mon, 16 Jun 2014 09:21:00 -0000 [thread overview] Message-ID: <bug-61430-4-txegewAXGd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61430-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61430 --- Comment #4 from christophe.lyon at st dot com --- Since commit 211625: 2014-06-13 Richard Biener <rguenther@suse.de> * tree-ssa-pre.c (eliminate_dom_walker::before_dom_children): Rewrite to propagate the VN result into all uses where possible and to remove stmts becoming dead because of that. (eliminate): Generalize stmt removal handling, remove in reverse dominator order to support proper debug stmt generation. Update stmts before removing stmts. * tree-ssa-propagate.c (propagate_tree_value): Remove bogus assert. The same error now appears when building other GCC configurations: --target mode --with-cpu --with-fpu arm-none-linux-gnueabi arm cortex-a9 default arm-none-linux-gnueabihf arm cortex-a9 neon-fp16 arm-none-linux-gnueabihf arm cortex-a9 vfp arm-none-linux-gnueabihf arm cortex-a15 neon-vfpv4 armeb-none-linux-gnueabihf arm cortex-a9 neon-fp16 Vladimir, can you have a look?
next prev parent reply other threads:[~2014-06-16 9:21 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-06 15:33 [Bug middle-end/61430] New: " christophe.lyon at st dot com 2014-06-06 15:33 ` [Bug middle-end/61430] " christophe.lyon at st dot com 2014-06-06 15:41 ` rguenth at gcc dot gnu.org 2014-06-06 16:09 ` christophe.lyon at st dot com 2014-06-16 9:21 ` christophe.lyon at st dot com [this message] 2014-06-16 9:48 ` jgreenhalgh at gcc dot gnu.org 2014-06-16 9:59 ` cltang at gcc dot gnu.org 2014-06-17 6:55 ` ramana 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-61430-4-txegewAXGd@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).