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/21829] [4.1/4.2 Regression] missed jump threading after unroller Date: Tue, 21 Mar 2006 05:10:00 -0000 [thread overview] Message-ID: <20060321051052.8666.qmail@sourceware.org> (raw) In-Reply-To: <bug-21829-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from law at redhat dot com 2006-03-21 05:10 ------- Today's patch picks up the missed const-propagation and allows simplification of the modulo operation. THere's still the opportunitity to use range information to simplify a conditional. However, fixing that is just basically iterating VRP in response to CFG changes -- not something we're going to do as it's simply too expensive. Thus I'm changing the state of this bug to WONTFIX. -- law at redhat dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21829
next prev parent reply other threads:[~2006-03-21 5:10 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-21829-6528@http.gcc.gnu.org/bugzilla/> 2005-10-29 15:52 ` [Bug tree-optimization/21829] [4.1 " pinskia at gcc dot gnu dot org 2005-10-30 23:32 ` pinskia at gcc dot gnu dot org 2006-02-09 3:20 ` [Bug tree-optimization/21829] [4.1/4.2 " law at redhat dot com 2006-02-11 0:59 ` pinskia at gcc dot gnu dot org 2006-02-28 20:39 ` mmitchel at gcc dot gnu dot org 2006-03-21 5:09 ` law at redhat dot com 2006-03-21 5:10 ` law at redhat dot com [this message] 2006-03-22 11:14 ` richard dot guenther at gmail dot com 2006-03-22 14:01 ` law at redhat dot com 2006-03-22 15:06 ` richard dot guenther at gmail dot com 2006-03-22 15:36 ` law at redhat dot com 2006-03-28 19:14 ` law at redhat dot com 2006-03-30 17:15 ` law at redhat dot com
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=20060321051052.8666.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).