On Wed, Aug 26, 2009 at 03:02:44PM -0400, Bradley Lucier wrote:
> On Wed, 2009-08-26 at 20:38 +0200, Paolo Bonzini wrote:
> >
> > > When I worked at AMD, I was starting to suspect that it may be more
> > > beneficial
> > > to re-enable the first schedule insns pass if you were compiling in 64-bit
Bradley Lucier writes:
> and RBX is used by XLAT, XLATB.
XLAT* is generally not used anymore, certainly not in gcc generated code.
> Are 12 registers not enough, in principle, to do scheduling before
> register allocation?
You want to limit gcc to only 12 registers?
> I was getting a 15% sp
On Wed, 2009-08-26 at 17:12 -0700, Ian Lance Taylor wrote:
> 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 cas
Bradley Lucier 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 speedu
On Wed, 2009-08-26 at 20:38 +0200, Paolo Bonzini wrote:
>
> > When I worked at AMD, I was starting to suspect that it may be more
> > beneficial
> > to re-enable the first schedule insns pass if you were compiling in 64-bit
> > mode, since you have more registers available, and the new registers
When I worked at AMD, I was starting to suspect that it may be more beneficial
to re-enable the first schedule insns pass if you were compiling in 64-bit
mode, since you have more registers available, and the new registers do not
have hard wired uses, which in the past always meant a lot of spil
On Wed, Aug 26, 2009 at 06:30:44AM -0700, Ian Lance Taylor wrote:
> Bradley Lucier writes:
>
> > I've never seen the answer to the following question: Why do some
> > versions of gcc that I build not have string substitutions in error
> > messages?
>
> Perhaps you configured with --disable-intl
On Wed, 2009-08-26 at 09:00 -0400, Bradley Lucier wrote:
> I've never seen the answer to the following question: Why do some
> versions of gcc that I build not have string substitutions in error
> messages?
>
> I get things like this:
>
> [luc...@lambda-head lib]$ /pkgs/gcc-mainline/bin/gcc
Bradley Lucier writes:
> I've never seen the answer to the following question: Why do some
> versions of gcc that I build not have string substitutions in error
> messages?
Perhaps you configured with --disable-intl?
> So, is -fschedule-insns an option to be avoided?
-fschedule-insns should
I've never seen the answer to the following question: Why do some
versions of gcc that I build not have string substitutions in error
messages?
I get things like this:
[luc...@lambda-head lib]$ /pkgs/gcc-mainline/bin/gcc -mcpu=970 -m64 -
fschedule-insns -Wno-unused -O1 -fno-math-errno -fsc
10 matches
Mail list logo
