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/21883] [4.1 Regression] jump threading causing excessive code duplication
Date: Fri, 04 Nov 2005 20:11:00 -0000 [thread overview]
Message-ID: <20051104201148.7652.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21883-87@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from law at redhat dot com 2005-11-04 20:11 -------
Band-aid applied for 4.1; Steven's prototype patch may be a better solution as
it only simulates those statements which affect the conditional and doesn't
count those statements (they're likely going to disappear in addition to the
conditional)
Evaluation of Steven's patch should occur after 4.1 is branched.
--
law at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|4.1.0 |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21883
next prev parent reply other threads:[~2005-11-04 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-21883-87@http.gcc.gnu.org/bugzilla/>
2005-10-07 21:32 ` steven at gcc dot gnu dot org
2005-10-31 3:43 ` mmitchel at gcc dot gnu dot org
2005-11-01 1:56 ` law at redhat dot com
2005-11-03 1:35 ` law at redhat dot com
2005-11-04 20:10 ` law at redhat dot com
2005-11-04 20:11 ` law at redhat dot com [this message]
2006-05-21 20:13 ` [Bug tree-optimization/21883] [4.1/4.2 " pinskia at gcc dot gnu dot org
2006-07-05 9:04 ` pinskia at gcc dot gnu dot org
2005-06-02 18:55 [Bug tree-optimization/21883] New: tree-ssa-dom.c " jakub at gcc dot gnu dot org
2005-06-02 19:04 ` [Bug tree-optimization/21883] [4.1 Regression] jump threading " pinskia at gcc dot gnu dot org
2005-07-12 6:43 ` pinskia at gcc dot gnu dot org
2005-09-01 11:23 ` steven at gcc dot gnu dot org
2005-09-01 11:37 ` 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=20051104201148.7652.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: link
Be 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).