A gcc-cris bug?

Dave Korn dk@artimi.com
Wed Oct 6 12:48:00 GMT 2004


> -----Original Message-----
> From: Diego Novillo 
> Sent: 06 October 2004 13:03

> On Wed, 2004-10-06 at 07:45, Dave Korn wrote:
> 
> > dk@mace /artimi> time ./foo.exe
> > foo is: 0, i is: 0
> > 
> > real    0m3.370s
> > user    0m3.343s
> > sys     0m0.015s
> > dk@mace /artimi>
> > 
> Apparently fixed in mainline:
> 
> $ time ./a
> foo is: 0, i is: 1
> 
> real    0m0.002s
> user    0m0.001s
> sys     0m0.001s

  Heh, yeh, I was able to infer from Andrew's source listing that it wasn't
going to take long to execute! :)

  Hmm.  Bad timing in the release cycle to bring this up though.  Might be
worth looking at in time for 3.3.6, though, would be nice to knock it on the
head before the branch gets closed.


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....



More information about the Gcc mailing list