public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/15678] [4.0/4.1 Regression] CSiBE i686 compilation time increased by 8% at -O2
Date: Sun, 30 Oct 2005 22:31:00 -0000 [thread overview]
Message-ID: <20051030223142.487.qmail@sourceware.org> (raw)
In-Reply-To: <bug-15678-8630@http.gcc.gnu.org/bugzilla/>
------- Comment #22 from mmitchel at gcc dot gnu dot org 2005-10-30 22:31 -------
According to the data in Comment #19, we're now better on some cases, and worse
on others. I'd suggest we just close this PR.
However, in the meanwhile, I've downgraded this to P4. A small compile-time
increase isn't going to block the upcoming releases.
--
mmitchel at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P2 |P4
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15678
next parent reply other threads:[~2005-10-30 22:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15678-8630@http.gcc.gnu.org/bugzilla/>
2005-10-30 22:31 ` mmitchel at gcc dot gnu dot org [this message]
2006-03-11 3:20 ` [Bug tree-optimization/15678] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org
2006-08-15 18:39 ` pinskia at gcc dot gnu dot org
2006-09-09 10:54 ` steven at gcc dot gnu dot org
2006-09-09 10:54 ` steven at gcc dot gnu dot org
2004-05-27 19:40 [Bug translation/15678] New: Compilation time increased by 10-20% gertom at inf dot u-szeged dot hu
2005-04-21 5:03 ` [Bug tree-optimization/15678] [4.0/4.1 Regression] CSiBE i686 compilation time increased by 8% at -O2 mmitchel at gcc dot gnu dot org
2005-07-08 1:45 ` mmitchel at gcc dot gnu dot org
2005-07-25 3:18 ` pinskia at gcc dot gnu dot org
2005-07-25 3:27 ` pinskia at gcc dot gnu dot org
2005-09-27 16:22 ` mmitchel 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=20051030223142.487.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).