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

--- Comment #1 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <[email protected]>:

https://gcc.gnu.org/g:6a4cfad20b7f7eacb352aed01b6159baa9935f2a

commit r17-647-g6a4cfad20b7f7eacb352aed01b6159baa9935f2a
Author: Jonathan Wakely <[email protected]>
Date:   Tue May 19 17:44:44 2026 +0100

    libstdc++: Deprecate numeric_limits::has_denorm for C++23

    The paper P2614R2 was approved in Issaquah, 2023. It deprecates the
    float_denorm_style enumeration type, its enumerators, and the
    numeric_limits::has_denorm and numeric_limits::has_denorm_loss static
    data members.

    The std/ranges/iota/max_size_type.cc test doesn't get warnings for using
    numeric_limits::has_denorm{,_loss} because of PR c++/125406. If that
    gets fixed, we'll need two new dg-warning lines in that test.

    libstdc++-v3/ChangeLog:

            * doc/xml/manual/evolution.xml: Document deprecations.
            * doc/html/manual/api.html: Regenerate.
            * include/bits/max_size_type.h (numeric_limits::has_denorm):
            Mark as deprecated.
            (numeric_limits::has_denorm_loss): Likewise.
            * include/std/limits (float_denorm_style): Mark as deprecated.
            (numeric_limits::has_denorm, numeric_limits::has_denorm_loss):
            Mark as deprecated.
            * testsuite/18_support/numeric_limits/char16_32_t.cc: Add
            dg-warning for expected deprecation warnings.
            * testsuite/18_support/numeric_limits/char8_t.cc: Likewise.
            * testsuite/18_support/numeric_limits/denorm_min.cc: Likewise.
            * testsuite/18_support/numeric_limits/dr559.cc: Likewise.
            *
testsuite/18_support/numeric_limits/requirements/constexpr_data.cc:
            Likewise.
            *
testsuite/18_support/numeric_limits/specialization_default_values.cc:
            Likewise.
            * testsuite/std/ranges/iota/max_size_type.cc: Likewise.

    Reviewed-by: Tomasz KamiÅski <[email protected]>

Reply via email to