Re: [PATCH] gdb: fix nan in scoped_time_it output

[Simon Marchi <simon.marchi@polymtl.ca>]

On 2026-09-28 17:59, Andrew Burgess wrote:
> simon.marchi@polymtl.ca writes:
> 
>> From: Simon Marchi <simon.marchi@efficios.com>
>>
>> With "maintenance set per-command time on", a scope that takes less
>> than a millisecond prints:
>>
>>   Time for "...": wall 0.000, user 0.000, sys 0.000, user+sys 0.000, -nan % CPU
>>
>> The durations are converted to an integer millisecond count before the
>> CPU usage is computed, so a sub-millisecond scope truncates the wall
>> time to zero, and the division produces a NaN (or an infinity, if the
>> CPU time is not zero).  We don't really care about sub-millisecond
>> durations for the purpose of this tool, so just add a check for
>> `wall_ms == 0`, and report the CPU usage as 0% if true.  This is purely
>> cosmetic.
> 
> LGTM.
> 
> Approved-By: Andrew Burgess <aburgess@redhat.com>

Thanks, pushed.

Simon