mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Erwin Rol <>
Subject: Re: [ptxdist] year 2038 Toolchain
Date: Mon, 27 May 2024 10:32:01 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 5/24/24 12:19, Michael Olbrich wrote:
> On Fri, May 24, 2024 at 11:04:24AM +0200, Erwin Rol wrote:
>> On 5/24/24 10:41, Ian Abbott wrote:
>>>> If I figure it out I'll let you guys know (so it can be added to the
>>>> official Toolchain)
>>> Rememember to define _FILE_OFFSET_BITS=64 too if it is not already
>>> defined. _TIME_BITS=64 is ineffective when _FILE_OFFSET_BITS=32 for
>>> Glibc policy reasons.
>> I tried some things to convince the Toolchain project (latest gcc13 release)
>> to use those two defines, but without much luck. Sometimes parts complained
>> that there were duplicate declarations of (time) functions, with some other
>> tries it actually complained the the _FILE_OFFSET_BITS was missing for some
>> part, that I really don't understand because I added them always in pairs.
>> So I believe it is just a bit too early for 100% year 2038 compliance at the
>> moment. Especially when it comes to C++/libstd++ there is also not much info
>> online.
>> But the C part seems to work with the support ptxdist offers, and C++ has
>> always been some unwanted stepchild, especially now Rust is going to safe
>> the world :-)
> So gcc-14 has a --enable-year2038 configure option, but I didn't test if it
> works.

Any ETA for a gcc14 ptxdist Toolchain ?

> But I don't know if that causes any API or ABI incompatibilities.
> The changelog says "Disable year2038 by default on 32-bit hosts.". That
> looks a bit suspicious to me.

Maybe make 2 specific 32bit toolchains, one with TIME_BITS=32 and one 
with TIME_BITS=64? So ppl (like me) can start testing the TIME_BITS=64 
version, and ppl that know for sure they do not care about y2038 can 
keep using the TIME_BITS=32 version ?

- Erwin

  reply	other threads:[~2024-05-27  8:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23  6:41 Erwin Rol
2024-05-23 10:38 ` Ian Abbott
2024-05-23 11:52   ` Erwin Rol
2024-05-24  8:41     ` Ian Abbott
2024-05-24  9:04       ` Erwin Rol
2024-05-24 10:19         ` Michael Olbrich
2024-05-27  8:32           ` Erwin Rol [this message]
2024-05-27 10:34             ` Christian Melki
2024-05-23  6:57 Erwin Rol

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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