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 tree-optimization/60766] [4.7/4.8 Regression] Wrong optimization with -O2 Date: Tue, 06 May 2014 09:02:00 -0000 [thread overview] Message-ID: <bug-60766-4-CPRKvvXTe0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60766-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60766 --- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> --- Author: rguenth Date: Tue May 6 09:02:08 2014 New Revision: 210099 URL: http://gcc.gnu.org/viewcvs?rev=210099&root=gcc&view=rev Log: 2014-05-06 Richard Biener <rguenther@suse.de> Backport from mainline 2014-04-17 Richard Biener <rguenther@suse.de> PR middle-end/60849 * tree-ssa-propagate.c (valid_gimple_rhs_p): Only allow effective boolean results for comparisons. * g++.dg/opt/pr60849.C: New testcase. 2014-04-07 Richard Biener <rguenther@suse.de> PR tree-optimization/60766 * tree-ssa-loop-ivopts.c (cand_value_at): Compute in an unsigned type. (may_eliminate_iv): Convert cand_value_at result to desired type. * gcc.dg/torture/pr60766.c: New testcase. 2014-04-23 Richard Biener <rguenther@suse.de> PR tree-optimization/60903 * tree-ssa-loop-im.c (execute_sm_if_changed): Properly apply IRREDUCIBLE_LOOP loop flags to newly created BBs and edges. * gcc.dg/torture/pr60903.c: New testcase. Added: branches/gcc-4_8-branch/gcc/testsuite/g++.dg/opt/pr60849.C branches/gcc-4_8-branch/gcc/testsuite/gcc.dg/torture/pr60766.c branches/gcc-4_8-branch/gcc/testsuite/gcc.dg/torture/pr60903.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-loop-im.c branches/gcc-4_8-branch/gcc/tree-ssa-loop-ivopts.c branches/gcc-4_8-branch/gcc/tree-ssa-propagate.c
next prev parent reply other threads:[~2014-05-06 9:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-60766-4@http.gcc.gnu.org/bugzilla/> 2014-04-05 0:05 ` [Bug tree-optimization/60766] [4.8/4.9 " pinskia at gcc dot gnu.org 2014-04-05 8:04 ` Joost.VandeVondele at mat dot ethz.ch 2014-04-06 8:20 ` netheril96 at gmail dot com 2014-04-06 12:44 ` mikpelinux at gmail dot com 2014-04-07 10:26 ` [Bug tree-optimization/60766] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org 2014-04-07 14:04 ` rguenth at gcc dot gnu.org 2014-04-07 14:10 ` [Bug tree-optimization/60766] [4.7/4.8 " rguenth at gcc dot gnu.org 2014-05-06 9:02 ` rguenth at gcc dot gnu.org [this message] 2014-05-06 9:03 ` [Bug tree-optimization/60766] [4.7 " rguenth at gcc dot gnu.org 2014-06-12 13:38 ` 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-60766-4-CPRKvvXTe0@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).