public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/32120] missed PRE/FRE of a*2+4 and (a+2)*2 Date: Tue, 13 Mar 2012 03:22:00 -0000 [thread overview] Message-ID: <bug-32120-4-fSmgvzuqvI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-32120-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32120 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW Blocks|22586 | Depends on| |22586 --- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-03-13 03:20:53 UTC --- I am not working on this any more. This really should be done correctly in FRE/PRE when looking up SSA_NAME * 4, and SSA_NAME is defined by a PLUS_EXPR with a constant, lookup the inner most SSA_NAME *4. Which is what PR 22586 is talking about. I might work towards that but not with my tree combine branch.
next prev parent reply other threads:[~2012-03-13 3:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-32120-4@http.gcc.gnu.org/bugzilla/> 2012-03-03 23:44 ` pinskia at gcc dot gnu.org 2012-03-04 0:46 ` pinskia at gcc dot gnu.org 2012-03-05 17:21 ` dberlin at gcc dot gnu.org 2012-03-05 17:33 ` rguenth at gcc dot gnu.org 2012-03-06 12:06 ` matz at gcc dot gnu.org 2012-03-13 3:22 ` pinskia at gcc dot gnu.org [this message] 2012-06-27 21:48 ` wschmidt at gcc dot gnu.org 2007-05-28 7:22 [Bug tree-optimization/32120] New: " pinskia at gcc dot gnu dot org 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-4-fSmgvzuqvI@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).