[PATCH v2] [libstdc++] [testsuite] avoid async.cc loss of precision [PR91486]

[Alexandre Oliva]

On Aug  1, 2024, Alexandre Oliva <oliva@adacore.com> wrote:

> Each iteration calls float_steady_clock::now() [...] an extra iteration
> will reach 5 and cause the test to fail.

> (Do we really want to use floats, that even with this tweak have
> borderline precision for sub-µs vs 1s deltas?  Do we want to make sure
> the wait time computation ensures we'll get past the deadline when the
> time is converted back to the given clock?)

Ping?
https://gcc.gnu.org/pipermail/gcc-patches/2024-August/658977.html

> for  libstdc++-v3/ChangeLog

> 	PR libstdc++/91486
> 	* testsuite/30_threads/async/async.cc
> 	(test_pr91486_wait_for): Mark status as unused.
> 	(test_pr91486_wait_until): Likewise.  Initialize epoch later.

-- 
Alexandre Oliva, happy hacker            https://FSFLA.org/blogs/lxo/
   Free Software Activist                   GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity
Excluding neuro-others for not behaving ""normal"" is *not* inclusive