https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117214
--- Comment #9 from XU Kailiang ---
(In reply to Jonathan Wakely from comment #7)
> So we should never use __timepunct directly (unless the formatting locale is
> the classic locale, and profiling shows it's faster to format directly
> instead o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118964
XU Kailiang changed:
What|Removed |Added
CC||xu2k3l4 at outlook dot com
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117214
--- Comment #4 from XU Kailiang ---
(In reply to Jonathan Wakely from comment #3)
> Patch posted to the list (thanks!):
>
> https://gcc.gnu.org/pipermail/gcc-patches/2025-January/674531.html
This patch seems not well formatted. I re-sent a re-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117214
--- Comment #2 from XU Kailiang ---
Is this patch usable? Steps to setup struct tm are copied from other functions
in chrono_io.h. Hope I didn't get them wrong.
--- a/libstdc++-v3/include/bits/chrono_io.h
+++ b/libstdc++-v3/include/bits/chrono_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117214
Bug ID: 117214
Summary: chrono format error for time point using %c: D_T_FMT
cannot be directly used as chrono-specs
Product: gcc
Version: 14.2.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117085
XU Kailiang changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117085
Bug ID: 117085
Summary: chrono formatting: %c does not honor locale after
expansion
Product: gcc
Version: 14.2.1
Status: UNCONFIRMED
Severity: normal
