public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/99832] New: std::chrono::system_clock::to_time_t needs ABI tag for 32-bit time_t Date: Tue, 30 Mar 2021 16:01:09 +0000 [thread overview] Message-ID: <bug-99832-4@http.gcc.gnu.org/bugzilla/> (raw) 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.
next reply other threads:[~2021-03-30 16:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-30 16:01 redi at gcc dot gnu.org [this message] 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
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-99832-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).