https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125112
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2026-04-30
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Felix Morgner from comment #3)
> Sorry for not including that output. Yes your assumption is correct. Here is
> the requested output:
>
> [...]
Thanks
> Regarding my note: I only mentioned it since it means that a "broken build"
> would have been acceptable in C++20 mode, at least according to the
> standard,
Hah, yes, that's true!
"Sorry that <ranges> doesn't compile, but it's not freestanding anyway!"
I hope that GCC 17 will support more of the C++23 and C++26 freestanding
changes.
