public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/111826] New: __cpp_lib_format should be 202110, not 202106
@ 2023-10-15 21:39 bbi5291 at gmail dot com
  2023-10-16  8:45 ` [Bug libstdc++/111826] " redi at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: bbi5291 at gmail dot com @ 2023-10-15 21:39 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 111826
           Summary: __cpp_lib_format should be 202110, not 202106
           Product: gcc
           Version: 13.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bbi5291 at gmail dot com
  Target Milestone: ---

libstdc++ 13.1 supports std::format including P2372 and P2418, which were
adopted in Oct 2021 and bumped the feature test macro to 202110L. But libstdc++
still defines `__cpp_lib_format` as 202106L.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/111826] __cpp_lib_format should be 202110, not 202106
  2023-10-15 21:39 [Bug libstdc++/111826] New: __cpp_lib_format should be 202110, not 202106 bbi5291 at gmail dot com
@ 2023-10-16  8:45 ` redi at gcc dot gnu.org
  2023-12-08 14:44 ` redi at gcc dot gnu.org
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2023-10-16  8:45 UTC (permalink / raw)
  To: gcc-bugs

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2023-10-16

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/111826] __cpp_lib_format should be 202110, not 202106
  2023-10-15 21:39 [Bug libstdc++/111826] New: __cpp_lib_format should be 202110, not 202106 bbi5291 at gmail dot com
  2023-10-16  8:45 ` [Bug libstdc++/111826] " redi at gcc dot gnu.org
@ 2023-12-08 14:44 ` redi at gcc dot gnu.org
  2023-12-09 14:07 ` cvs-commit at gcc dot gnu.org
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2023-12-08 14:44 UTC (permalink / raw)
  To: gcc-bugs

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
   Target Milestone|---                         |13.3
           Assignee|unassigned at gcc dot gnu.org      |redi at gcc dot gnu.org

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/111826] __cpp_lib_format should be 202110, not 202106
  2023-10-15 21:39 [Bug libstdc++/111826] New: __cpp_lib_format should be 202110, not 202106 bbi5291 at gmail dot com
  2023-10-16  8:45 ` [Bug libstdc++/111826] " redi at gcc dot gnu.org
  2023-12-08 14:44 ` redi at gcc dot gnu.org
@ 2023-12-09 14:07 ` cvs-commit at gcc dot gnu.org
  2023-12-09 22:04 ` cvs-commit at gcc dot gnu.org
  2023-12-09 22:05 ` redi at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2023-12-09 14:07 UTC (permalink / raw)
  To: gcc-bugs

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

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

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

commit r14-6358-gcdf45e00a936a76a785c592c9730f24ef1ac25cd
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Dec 8 14:40:26 2023 +0000

    libstdc++: Fix value of __cpp_lib_format macro [PR111826]

    As noted in the PR, we support both features required for the 202110L
    value, so we should define it with that value.

    libstdc++-v3/ChangeLog:

            PR libstdc++/111826
            * include/bits/version.def (format): Update value.
            * include/bits/version.h: Regenerate.
            * testsuite/std/format/functions/format.cc:

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/111826] __cpp_lib_format should be 202110, not 202106
  2023-10-15 21:39 [Bug libstdc++/111826] New: __cpp_lib_format should be 202110, not 202106 bbi5291 at gmail dot com
                   ` (2 preceding siblings ...)
  2023-12-09 14:07 ` cvs-commit at gcc dot gnu.org
@ 2023-12-09 22:04 ` cvs-commit at gcc dot gnu.org
  2023-12-09 22:05 ` redi at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2023-12-09 22:04 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:9f5011f9e6e347e0b91f47a118a0ce58a2c2d99a

commit r13-8140-g9f5011f9e6e347e0b91f47a118a0ce58a2c2d99a
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Dec 8 14:40:26 2023 +0000

    libstdc++: Fix value of __cpp_lib_format macro [PR111826]

    As noted in the PR, we support both features required for the 202110L
    value, so we should define it with that value.

    libstdc++-v3/ChangeLog:

            PR libstdc++/111826
            * include/std/format (__cpp_lib_format): Update value.
            * include/std/version (__cpp_lib_format): Likewise.
            * testsuite/std/format/functions/format.cc: Update expected
            value.

    (cherry picked from commit cdf45e00a936a76a785c592c9730f24ef1ac25cd)

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/111826] __cpp_lib_format should be 202110, not 202106
  2023-10-15 21:39 [Bug libstdc++/111826] New: __cpp_lib_format should be 202110, not 202106 bbi5291 at gmail dot com
                   ` (3 preceding siblings ...)
  2023-12-09 22:04 ` cvs-commit at gcc dot gnu.org
@ 2023-12-09 22:05 ` redi at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2023-12-09 22:05 UTC (permalink / raw)
  To: gcc-bugs

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed, thanks for the report.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2023-12-09 22:05 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-15 21:39 [Bug libstdc++/111826] New: __cpp_lib_format should be 202110, not 202106 bbi5291 at gmail dot com
2023-10-16  8:45 ` [Bug libstdc++/111826] " redi at gcc dot gnu.org
2023-12-08 14:44 ` redi at gcc dot gnu.org
2023-12-09 14:07 ` cvs-commit at gcc dot gnu.org
2023-12-09 22:04 ` cvs-commit at gcc dot gnu.org
2023-12-09 22:05 ` redi at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).