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/55281] [4.8 Regression] ICE in build_int_cst_wide, at tree.c:1217 (with Ofast, ok with O3) Date: Mon, 12 Nov 2012 16:23:00 -0000 [thread overview] Message-ID: <bug-55281-4-i55g2msrqz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55281-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55281 --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-11-12 16:23:29 UTC --- I'm just testing that, so I know it doesn't have side-effects. COND_EXPR handling which I've copied was doing the same thing. The reason for the fold-const.c change was that while you handle that case in forwprop, it only triggers if forwprop actually simplifies the condition, but if e.g. copyprop does that, then nothing will fix it up afterwards till expansion.
next prev parent reply other threads:[~2012-11-12 16:23 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-12 10:06 [Bug tree-optimization/55281] New: " vincenzo.innocente at cern dot ch 2012-11-12 10:33 ` [Bug tree-optimization/55281] " jakub at gcc dot gnu.org 2012-11-12 11:46 ` jakub at gcc dot gnu.org 2012-11-12 15:12 ` jakub at gcc dot gnu.org 2012-11-12 15:37 ` vincenzo.innocente at cern dot ch 2012-11-12 16:19 ` glisse at gcc dot gnu.org 2012-11-12 16:23 ` jakub at gcc dot gnu.org [this message] 2012-11-12 16:39 ` glisse at gcc dot gnu.org 2012-11-13 7:26 ` jakub at gcc dot gnu.org 2012-11-13 7:44 ` jakub at gcc dot gnu.org 2012-11-13 8:04 ` vincenzo.innocente at cern dot ch
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-55281-4-i55g2msrqz@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).