public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/18046] Missed jump threading optimization Date: Tue, 21 Mar 2006 15:57:00 -0000 [thread overview] Message-ID: <20060321155746.29228.qmail@sourceware.org> (raw) In-Reply-To: <bug-18046-280@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from law at redhat dot com 2006-03-21 15:57 ------- We've got zero chance of threading the jump in this case until the partially redundant load from "i" is removed. Daniel -- there's a pretty obvious redundant load from the global variable "i" in this testcase. I haven't investigated why PRE is missing this obvious redundancy. Jeff -- law at redhat dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dberlin at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18046
next prev parent reply other threads:[~2006-03-21 15:57 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-18046-280@http.gcc.gnu.org/bugzilla/> 2005-10-07 21:21 ` steven at gcc dot gnu dot org 2006-03-21 15:57 ` law at redhat dot com [this message] 2006-03-21 16:05 ` pinskia at gcc dot gnu dot org 2006-03-21 16:57 ` dberlin at dberlin dot org 2008-09-21 14:00 ` steven at gcc dot gnu dot org 2008-09-23 21:56 ` law at redhat dot com 2010-02-04 22:52 ` steven at gcc dot gnu dot org 2010-07-13 10:30 ` steven at gcc dot gnu dot org [not found] <bug-18046-4@http.gcc.gnu.org/bugzilla/> 2011-07-20 0:34 ` pinskia at gcc dot gnu.org 2012-11-08 22:30 ` steven at gcc dot gnu.org 2004-10-18 12:16 [Bug tree-optimization/18046] New: " steven at gcc dot gnu dot org 2004-10-18 12:52 ` [Bug tree-optimization/18046] " pinskia at gcc dot gnu dot org 2004-10-18 13:22 ` steven at gcc dot gnu dot org 2004-10-18 17:30 ` steven at gcc dot gnu dot org 2004-10-18 18:31 ` law at redhat dot com 2004-10-18 22:50 ` stevenb at suse dot de 2004-10-19 20:16 ` law at redhat dot com 2005-04-23 16:58 ` steven 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=20060321155746.29228.qmail@sourceware.org \ --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).