This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] increase timeout in simulate-thread gdb test

On Wed, Feb 08, 2012 at 09:00:00AM -0500, Andrew MacLeod wrote:
> On 02/08/2012 08:37 AM, Iain Sandoe wrote:
>>> Well - it depends.  You don't know whether the test will eventually  
>>> terminate,
>>> but yes, you could interpret "UNRESOLVED" as exactly what that is.  A
>>> definite finishes-never would be a FAIL of course.  The question is  
>>> on which
>>> side to err.
>> There was also some discussion about reducing the amount of log-file  
>> output (which might help too).
>> Did that ever get anywhere/who would be willing to decide what could  
>> be dropped from the output?
>> Iain
> For a start we could comment out the
>    disp/i $pc
> command in the simulate-thread.gdb script file.   I'd leave it there as  
> a comment to make it easy to turn back on when needed.

   Eliminating the "disp/i $pc" in the simulate-thread.gdb script file
is insufficient to reduce the execution time below 10 seconds. What is 
the next thing we can prune?

> You can still see the source line being executed, and you generally need  
> to take the test case and hand run it to see whats going on anyway.    
> That cuts the log file in about half.
> Andrew

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]