https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #12 from GCC Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:a5aca83ca9c7fac895d10eb7b3e14b1927ec1eac
commit r13-8263-ga5aca83ca9c7fac895d10eb7b3e14b1927ec1eac
Author: Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #11 from hirtham...@allterra-dno.de ---
(In reply to Jonathan Wakely from comment #7)
> (In reply to Jonathan Wakely from comment #6)
> > (In reply to Hirthammer from comment #5)
> > > This whole thing with std::format and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #10 from Jonathan Wakely ---
Fixed on trunk so far.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #9 from GCC Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:7431fcea6b72beb54abb1932c254ac0e76bd0bde
commit r14-8321-g7431fcea6b72beb54abb1932c254ac0e76bd0bde
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #8 from Jonathan Wakely ---
I am testing a patch that allows writing floating-point utc_time, gps_time etc.
with any format string, and allows writing floating-point sys_time with a
non-empty spec.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #7 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #6)
> (In reply to Hirthammer from comment #5)
> > This whole thing with std::format and std::chrono::time_point is currently a
> > total minefield.
>
> That
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #6 from Jonathan Wakely ---
(In reply to Hirthammer from comment #5)
> This whole thing with std::format and std::chrono::time_point is currently a
> total minefield.
That seems like an exaggeration.
> In MSVC it is even more
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #5 from hirtham...@allterra-dno.de ---
(In reply to Jonathan Wakely from comment #4)
> MSVC rejects this the same way, although libc++ from LLVM 17 compiles it.
>
> AFAICT std::format("{}", tp) would be invalid because that formats
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #4 from Jonathan Wakely ---
MSVC rejects this the same way, although libc++ from LLVM 17 compiles it.
AFAICT std::format("{}", tp) would be invalid because that formats tp by
writing to a stream, and there is no operator<< for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #3 from hirtham...@allterra-dno.de ---
Sorry, for the missing includes.
> Since this is a bug in libstdc++ headers it's not at all surprising that you
> get
> the same error with any compiler using those headers. This should not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #2 from Jonathan Wakely ---
(In reply to Hirthammer from comment #0)
> Consider the following code snippet:
As stated at https://gcc.gnu.org/bugs we want a complete test case, not a
snippet.
#include
#include
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |13.3
Assignee|unassigned
13 matches
Mail list logo