[Bug testsuite/113175] [11/12/13/14 Regression] testsuite/std/ranges/iota/max_size_type.cc 5x times slower

[cvs-commit at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113175

--- Comment #11 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Patrick Palka
<ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:af767e0b9e926fa1ef217087ce3b076be361965f

commit r13-8189-gaf767e0b9e926fa1ef217087ce3b076be361965f
Author: Patrick Palka <ppalka@redhat.com>
Date:   Tue Jan 2 21:31:20 2024 -0500

    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.

    (cherry picked from commit a138b99646a5551c53b860648521adb5bfe8c2fa)