public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/37367] [4.4/4.5 Regression] gcc-4.4/4.5 speed regression
Date: Sun, 21 Mar 2010 12:20:00 -0000 [thread overview]
Message-ID: <20100321122012.17869.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37367-12873@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from steven at gcc dot gnu dot org 2010-03-21 12:20 -------
Bug in WAITING for a long time, no feedback. Very small, hard-to-catch code
difference. It's been noted before that the core2 scheduler description
(contributed by Intel itself!) often results in worse code than the generic
scheduler description. All in all, no reason to track this anymore.
--
steven at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37367
next prev parent reply other threads:[~2010-03-21 12:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 10:03 [Bug other/37367] New: gcc-4.4 " tim at klingt dot org
2008-09-06 21:45 ` [Bug target/37367] [4.4 Regression] " pinskia at gcc dot gnu dot org
2008-10-22 3:07 ` mmitchel at gcc dot gnu dot org
2009-01-31 14:19 ` bonzini at gnu dot org
2009-01-31 14:33 ` rguenth at gcc dot gnu dot org
2009-02-05 22:03 ` rguenth at gcc dot gnu dot org
2009-04-21 16:00 ` [Bug target/37367] [4.4/4.5 Regression] gcc-4.4/4.5 " jakub at gcc dot gnu dot org
2009-07-22 10:33 ` jakub at gcc dot gnu dot org
2009-10-15 12:55 ` jakub at gcc dot gnu dot org
2010-01-21 13:18 ` jakub at gcc dot gnu dot org
2010-03-21 12:20 ` steven at gcc dot gnu dot org [this message]
2010-03-21 14:44 ` howarth at nitro dot med dot uc dot edu
2010-03-21 16:20 ` hjl dot tools at gmail dot com
2010-03-22 10:01 ` rguenther at suse dot de
2010-03-22 10:47 ` jakub at gcc dot gnu dot org
2010-03-22 10:49 ` jakub 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=20100321122012.17869.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).