diff options
| author | Patrick Palka <ppalka@redhat.com> | 2024-01-02 21:31:20 -0500 |
|---|---|---|
| committer | Patrick Palka <ppalka@redhat.com> | 2024-01-02 21:31:20 -0500 |
| commit | a138b99646a5551c53b860648521adb5bfe8c2fa (patch) | |
| tree | 38a6ba0a7a211a84e750410e6d45cdfa538e0134 /gcc/rust/util/rust-attributes.h | |
| parent | 45c807b79479a725c968db638ddd0fd5f25deeaa (diff) | |
| download | gcc-a138b99646a5551c53b860648521adb5bfe8c2fa.zip gcc-a138b99646a5551c53b860648521adb5bfe8c2fa.tar.gz gcc-a138b99646a5551c53b860648521adb5bfe8c2fa.tar.bz2 | |
libstdc++: testsuite: Reduce max_size_type.cc exec time [PR113175]
The adjustment to max_size_type.cc in r14-205-g83470a5cd4c3d2
inadvertently increased the execution time of this test by over 5x due
to making the two main loops actually run in the signed_p case instead
of being dead code.
To compensate, this patch cuts the relevant loops' range [-1000,1000] by
10x as proposed in the PR. This shouldn't significantly weaken the test
since the same important edge cases are still checked in the smaller range
and/or elsewhere. On my machine this reduces the test's execution time by
roughly 10x (and 1.6x relative to before r14-205).
PR testsuite/113175
libstdc++-v3/ChangeLog:
* testsuite/std/ranges/iota/max_size_type.cc (test02): Reduce
'limit' to 100 from 1000 and adjust 'log2_limit' accordingly.
(test03): Likewise.
Diffstat (limited to 'gcc/rust/util/rust-attributes.h')
0 files changed, 0 insertions, 0 deletions