public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/32120] New: missed PRE/FRE of a*2+4 and (a+2)*2 Date: Mon, 28 May 2007 07:22:00 -0000 [thread overview] Message-ID: <bug-32120-6528@http.gcc.gnu.org/bugzilla/> (raw) A testcase which we should optimize all the way to return true: int f(int a, int b) { int c = a+2; int d = c*2; int e = a*2; int f = e+4; return d == f; } -- Summary: missed PRE/FRE of a*2+4 and (a+2)*2 Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32120
next reply other threads:[~2007-05-28 7:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-28 7:22 pinskia at gcc dot gnu dot org [this message] 2007-05-28 10:27 ` [Bug tree-optimization/32120] " rguenth at gcc dot gnu dot org 2007-06-10 2:23 ` pinskia at gcc dot gnu dot org 2007-06-10 3:31 ` dberlin at gcc dot gnu dot org 2007-06-29 3:05 ` pinskia at gcc dot gnu dot org 2008-04-29 9:56 ` rguenth at gcc dot gnu dot 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-32120-6528@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).