[Bug libstdc++/71556] set::get_time() requires leading 0s for %H and friends

[redi at gcc dot gnu.org]

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

Jonathan Wakely  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #4 from Jonathan Wakely  ---
The leading zeros were required in C++98, but are optional since C++1.

This is Bug 45896.

*** This bug has been marked as a duplicate of bug 45896 ***

[Bug libstdc++/71556] set::get_time() requires leading 0s for %H and friends

[redi at gcc dot gnu.org]

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

Jonathan Wakely  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|unassigned at gcc dot gnu.org  |redi at gcc dot gnu.org

[Bug libstdc++/71556] set::get_time() requires leading 0s for %H and friends

[maxim.yegorushkin at gmail dot com]

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

Maxim Egorushkin  changed:

   What|Removed |Added

 CC||maxim.yegorushkin at gmail dot 
com

--- Comment #3 from Maxim Egorushkin  ---
People keep hitting this bug:
https://stackoverflow.com/questions/44901711/convert-ansi-cs-asctime-format-using-stdget-time

[Bug libstdc++/71556] set::get_time() requires leading 0s for %H and friends

[sebunger44 at gmail dot com]

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

Sebastian Unger  changed:

   What|Removed |Added

 CC||sebunger44 at gmail dot com

--- Comment #2 from Sebastian Unger  ---
I also just ran into this. Took me a while to convince myself that I was
actually looking at a compiler (well library) bug before searching.

clang does not have this issue.

It also affects %m and %d. Haven't tried any others.

[Bug libstdc++/71556] set::get_time() requires leading 0s for %H and friends

[redi at gcc dot gnu.org]

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

Jonathan Wakely  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2016-06-16
 Ever confirmed|0   |1

[Bug libstdc++/71556] set::get_time() requires leading 0s for %H and friends

[j...@jak-linux.org]

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

--- Comment #1 from Julian Andres Klode  ---
To be clear, while the attachment uses the (I assume still) non-standard
C.UTF-8, the same also happens with the C locale, and the "" locale in an
en_IE.UTF-8 environment.