public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "echristo at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/13931] [3.3/3.4/4.0 Regression] combiner much slower on big basic blocks Date: Tue, 07 Dec 2004 19:54:00 -0000 [thread overview] Message-ID: <20041207195434.19370.qmail@sourceware.org> (raw) In-Reply-To: <20040130124106.13931.bonzini@gnu.org> ------- Additional Comments From echristo at redhat dot com 2004-12-07 19:54 ------- The patch was put in to stop erroneous REG_DEAD notes from being created where they shouldn't IIRC. Now, we may be able to rerun cfg as Paolo suggests, but I don't know for certain. Unless we can prove that new speedups do the right thing all the time I don't think we can put them back in - there was even a note in the old code that we didn't always do the right thing. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13931
next prev parent reply other threads:[~2004-12-07 19:54 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-30 12:41 [Bug optimization/13931] New: combiner much slower on big functions bonzini at gnu dot org 2004-01-30 12:41 ` [Bug optimization/13931] " bonzini at gnu dot org 2004-01-30 12:42 ` bonzini at gnu dot org 2004-01-30 17:23 ` [Bug optimization/13931] [3.4/3.5 Regression] " pinskia at gcc dot gnu dot org 2004-01-30 19:26 ` [Bug optimization/13931] [3.4/3.5 Regression] combiner much slower on big basic blocks bonzini at gnu dot org 2004-01-30 19:26 ` bonzini at gnu dot org 2004-02-04 16:39 ` pinskia at gcc dot gnu dot org 2004-03-08 23:03 ` mmitchel at gcc dot gnu dot org 2004-06-07 3:24 ` [Bug rtl-optimization/13931] " pinskia at gcc dot gnu dot org 2004-06-07 19:08 ` [Bug rtl-optimization/13931] [3.3/3.4/3.5 " pinskia at gcc dot gnu dot org 2004-06-07 20:44 ` pinskia at gcc dot gnu dot org 2004-06-07 20:54 ` pinskia at gcc dot gnu dot org 2004-06-07 21:13 ` ebotcazou at gcc dot gnu dot org 2004-06-18 23:47 ` mmitchel at gcc dot gnu dot org 2004-08-29 18:47 ` mmitchel at gcc dot gnu dot org 2004-10-30 20:02 ` [Bug rtl-optimization/13931] [3.3/3.4/4.0 " mmitchel at gcc dot gnu dot org 2004-10-30 20:03 ` mmitchel at gcc dot gnu dot org 2004-11-15 12:11 ` ebotcazou at gcc dot gnu dot org 2004-11-16 8:05 ` ebotcazou at gcc dot gnu dot org 2004-11-16 8:22 ` ebotcazou at gcc dot gnu dot org 2004-11-16 8:24 ` ebotcazou at gcc dot gnu dot org 2004-11-18 20:46 ` pinskia at gcc dot gnu dot org 2004-12-07 19:54 ` echristo at redhat dot com [this message] 2004-12-22 19:23 ` steven at gcc dot gnu dot org 2004-12-22 19:48 ` echristo at redhat dot com [not found] <20040130124106.13931.bonzini@gcc.gnu.org> 2005-01-14 14:31 ` steven at gcc dot gnu dot org 2005-01-15 6:11 ` pinskia at gcc dot gnu dot org 2005-01-15 7:31 ` echristo at redhat dot com 2005-01-15 12:25 ` steven at gcc dot gnu dot org 2005-01-15 16:23 ` pinskia at gcc dot gnu dot org 2005-01-28 18:50 ` ian at airs 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=20041207195434.19370.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).