On Tue, Sep 05, 2006 at 01:27:45PM -0700, Steve Ellcey wrote:
> I am not sure what the 'right' way to do this is. I wound up editing
> /usr/share/dejagnu/remote.exp to change 'set timeout 300' to 'set
> timeout 2000' and I edited /usr/share/dejagnu/config/unix.exp to change
> 'set status [remote_
> From: Rask Ingemann Lambertsen <[EMAIL PROTECTED]>
>
>In case it isn't obvious, I have little or no clue about tcl, expect and
> dejagnu. The only time that I've had success in modifying the timeout was by
> adding this to /usr/share/dejagnu/baseboards/unix.exp:
>
> set_board_info gcc,timeou
On Tue, Aug 30, 2005 at 05:44:52PM -0700, Mike Stump wrote:
> On Aug 30, 2005, at 4:34 PM, Steve Ellcey wrote:
> >I see that it is timing out on a slow machine that I have. I tried
> >to look around to find out how and where the timeout limit was set
> >and could not find it.
[snip]
> M-x gr
> Yes, I think you are right. I can see a substantial slowdown in
> compilation times on IA64 HP-UX at -O2 (though it doesn't time out
> there).
>
> gcc 4.0.0 - 81 seconds
> gcc 3.4.1 - 38 seconds
> gcc 3.4.0 - 37 seconds
> gcc 3.3.5 - 89 seconds
> gcc 3.3.1 - 91 seconds
>
> 3.3 is slow, 3.4 is fa
> > By hand, I can compile the test in about 3 1/2 minutes on the machine in
> > question (the machine may have been busier when the failure occured and thus
> > taken longer).
>
> I think it's a real regression (memory consumption/speed) of the compiler, it
> is timing out on all the slow SPARC
> By hand, I can compile the test in about 3 1/2 minutes on the machine in
> question (the machine may have been busier when the failure occured and thus
> taken longer).
I think it's a real regression (memory consumption/speed) of the compiler, it
is timing out on all the slow SPARC machines I
On Aug 30, 2005, at 4:34 PM, Steve Ellcey wrote:
I see that it is timing out on a slow machine that I have. I tried
to look around to find out how and where the timeout limit was set
and could not find it. Can someone explain to me how much time a
compile is given and where this limit is s
I was looking at a failure of the test
gcc.c-torture/compile/20001226-1.c on one of my machines and I see that
it is timing out on a slow machine that I have. I tried to look around
to find out how and where the timeout limit was set and could not find
it. Can someone explain to me how much time
