From: Ian Lance Taylor <iant@google.com>
To: Bradley Lucier <lucier@math.purdue.edu>
Cc: Paolo Bonzini <bonzini@gnu.org>,
Michael Meissner <meissner@linux.vnet.ibm.com>,
GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Why no strings in error messages?
Date: Thu, 27 Aug 2009 02:54:00 -0000 [thread overview]
Message-ID: <m3ab1m2jza.fsf@google.com> (raw)
In-Reply-To: <1251313364.25086.194.camel@heine.math.purdue.edu> (Bradley Lucier's message of "Wed\, 26 Aug 2009 15\:02\:44 -0400")
Bradley Lucier <lucier@math.purdue.edu> writes:
> Are 12 registers not enough, in principle, to do scheduling before
> register allocation? I was getting a 15% speedup on some numerical
> codes, as pre-scheduling spaced out the vector loads among the
> floating-point computations.
If you are getting that kind of speedup (which I personally did not
expect) then this is clearly worth pursuing. It should be possible to
make it work at least in 64-bit mode. I recommend that you file a bug
report or two for cases which fail when using -fschedule-insns.
Ian
next prev parent reply other threads:[~2009-08-27 0:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 17:08 Bradley Lucier
2009-08-26 17:37 ` Ian Lance Taylor
2009-08-26 18:23 ` Michael Meissner
2009-08-26 20:48 ` Paolo Bonzini
2009-08-26 21:28 ` Paolo Bonzini
2009-08-26 21:37 ` Bradley Lucier
2009-08-27 2:54 ` Ian Lance Taylor [this message]
2009-08-27 10:05 ` Bradley Lucier
2009-08-27 18:40 ` Andi Kleen
2009-09-01 12:11 ` Gabriel Paubert
2009-08-26 17:48 ` Richard Earnshaw
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=m3ab1m2jza.fsf@google.com \
--to=iant@google.com \
--cc=bonzini@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=lucier@math.purdue.edu \
--cc=meissner@linux.vnet.ibm.com \
/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).