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] std::chrono::system_clock::to_time_t needs ABI tag for 32-bit time_t
Date: Wed, 31 Jan 2024 12:05:27 +0000	[thread overview]
Message-ID: <bug-99832-4-XQFti66dD1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99832-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> +// Since glibc 2.34 using -D_TIME_BITS=64 will enable 64-bit time_t
> +// for "legacy ABIs", i.e. ones that historically used 32-bit time_t.
> +// This internal glibc macro will be defined iff new 64-bit time_t is in
> use.

This is correct for current glibc releases, but in glibc master
__USE_TIME_BITS64 is defined unconditionally to 0 or 1 and tells you the size
of time_t, not whether it switched to 64-bit counter to the legacy ABI:
https://inbox.sourceware.org/libc-alpha/20240118131801.600373-1-adhemerval.zanella@linaro.org/

Yay.

  parent reply	other threads:[~2024-01-31 12:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 16:01 [Bug libstdc++/99832] New: " 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 [this message]
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-XQFti66dD1@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: link
Be 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).