public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39976] [4.5 Regression] Big sixtrack degradation on powerpc 32/64 after revision r146817
Date: Tue, 12 May 2009 15:29:00 -0000 [thread overview]
Message-ID: <20090512152910.6391.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39976-16550@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from pinskia at gcc dot gnu dot org 2009-05-12 15:29 -------
(In reply to comment #12)
> I'm working on a fix. Earlier compilers contained a hack for this (because
> swing modulo scheduling can only deal with single BB loops),
It was not just SMS which only can deal with single BB loops, that change
improved other loops in general because the register allocator was not able to
get rid of the extra basic block (just SMS showed it more). Since my name is
on that change, my motivation at the time the part of the patch was written was
not SMS (SMS was an after thought to me).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39976
next prev parent reply other threads:[~2009-05-12 15:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 16:25 [Bug regression/39976] New: " luisgpm at linux dot vnet dot ibm dot com
2009-04-30 16:57 ` [Bug middle-end/39976] " pinskia at gcc dot gnu dot org
2009-04-30 19:30 ` luisgpm at linux dot vnet dot ibm dot com
2009-04-30 19:39 ` luisgpm at linux dot vnet dot ibm dot com
2009-04-30 19:52 ` pinskia at gcc dot gnu dot org
2009-04-30 20:17 ` hjl dot tools at gmail dot com
2009-05-01 20:07 ` rguenth at gcc dot gnu dot org
2009-05-04 13:51 ` luisgpm at linux dot vnet dot ibm dot com
2009-05-04 14:37 ` matz at gcc dot gnu dot org
2009-05-04 15:41 ` luisgpm at linux dot vnet dot ibm dot com
2009-05-04 15:50 ` luisgpm at linux dot vnet dot ibm dot com
2009-05-04 16:10 ` matz at gcc dot gnu dot org
2009-05-05 15:52 ` mmitchel at gcc dot gnu dot org
2009-05-12 12:56 ` luisgpm at linux dot vnet dot ibm dot com
2009-05-12 13:38 ` matz at gcc dot gnu dot org
2009-05-12 15:29 ` pinskia at gcc dot gnu dot org [this message]
2009-05-13 18:17 ` matz at gcc dot gnu dot org
2009-05-13 20:15 ` matz at gcc dot gnu dot org
2009-05-14 4:12 ` luisgpm at linux dot vnet dot ibm dot com
2009-05-15 2:16 ` luisgpm at linux dot vnet dot ibm dot com
2009-05-15 2:19 ` luisgpm at linux dot vnet dot ibm dot com
2009-05-18 18:09 ` pthaugen at gcc dot gnu dot org
2009-05-21 10:40 ` rguenth at gcc dot gnu dot org
2009-06-03 3:01 ` luisgpm at linux dot vnet dot ibm dot com
2009-07-08 21:53 ` pthaugen at gcc dot gnu dot org
2009-07-09 10:43 ` matz at gcc dot gnu dot org
2009-07-14 21:15 ` pthaugen at gcc dot gnu dot org
2009-07-23 23:49 ` pthaugen at gcc dot gnu dot org
2009-11-30 13:14 ` rguenth at gcc dot gnu dot org
2009-11-30 21:29 ` pthaugen at gcc dot gnu dot org
2010-03-28 15:51 ` rguenth at gcc dot gnu dot org
2010-03-31 11:56 ` rguenth at gcc dot gnu dot org
2010-04-06 11:38 ` rguenth at gcc dot gnu dot org
2010-07-31 9:33 ` [Bug middle-end/39976] [4.5/4.6 " rguenth 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=20090512152910.6391.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).