aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorAlexandre Oliva <oliva@adacore.com>2024-09-02 11:32:03 -0300
committerAlexandre Oliva <oliva@gnu.org>2024-09-02 11:32:03 -0300
commitaf1500dd8c00df4541f7aa393ab7cf57db18241b (patch)
treef64b995a699c4175454384c167d9529aceb8ec67 /gcc
parent410061b15a9b0a464c851173fa568e49c85570dc (diff)
downloadgcc-af1500dd8c00df4541f7aa393ab7cf57db18241b.zip
gcc-af1500dd8c00df4541f7aa393ab7cf57db18241b.tar.gz
gcc-af1500dd8c00df4541f7aa393ab7cf57db18241b.tar.bz2
[libstdc++-v3] [testsuite] improve future/*/poll.cc calibration
30_threads/future/members/poll.cc has calibration code that, on systems with very low clock resolution, may spuriously fail to run. Even when it does run, low resolution and reasonable timeouts limit severely the viability of increasing the loop counts so as to reduce measurement noise, so we end up with very noisy results. On various vxworks targets, high iteration count (low-noise) measurements confirmed that some of the operations that we expected to be up to 100x slower than the fastest ones can run a little slower than that and, with significant noise, may seem to be even slower, comparatively. Bump the factors up to 200x, so that we have plenty of margin over measured results. for libstdc++-v3/ChangeLog * testsuite/30_threads/future/members/poll.cc: Factor out calibration, and run it unconditionally. Lower its strictness. Bump wait_until_*'s slowness factor.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions