public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/99832] New: std::chrono::system_clock::to_time_t needs ABI tag for 32-bit time_t
@ 2021-03-30 16:01 redi at gcc dot gnu.org
  2023-06-10  9:33 ` [Bug libstdc++/99832] " redi at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2021-03-30 16:01 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 99832
           Summary: std::chrono::system_clock::to_time_t needs ABI tag for
                    32-bit time_t
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Keywords: ABI
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: redi at gcc dot gnu.org
  Target Milestone: ---

chrono::system_clock defines:

      static std::time_t
      to_time_t(const time_point& __t) noexcept

This is a non-template function and its mangled name does not depend on the
return type. The mangled name is:

_ZNSt6chrono3_V212system_clock9to_time_tERKNS_10time_pointIS1_NS_8durationIlSt5ratioILl1ELl1000000000EEEEEE

For a target that allows time_t to be either 32-bit or 64-bit, we need this
mangled name to reflect the type of time_t.

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

end of thread, other threads:[~2024-05-07  7:39 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-30 16:01 [Bug libstdc++/99832] New: std::chrono::system_clock::to_time_t needs ABI tag for 32-bit time_t redi at gcc dot gnu.org
2023-06-10  9:33 ` [Bug libstdc++/99832] " redi at gcc dot gnu.org
2023-07-19 18:24 ` redi at gcc dot gnu.org
2024-01-31 11:49 ` redi at gcc dot gnu.org
2024-01-31 12:05 ` redi at gcc dot gnu.org
2024-05-07  7:39 ` rguenth 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).