mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Erwin Rol <mailinglists@erwinrol.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] year 2038 Toolchain
Date: Thu, 23 May 2024 08:57:44 +0200	[thread overview]
Message-ID: <4d22d190-aee5-4bb9-930d-dd78ecca593c@erwinrol.com> (raw)

Hey all,

I am working on arm32 (imx6ul) and need to support dates beyond 2038. 
With the new ptxdist 2038 support it seems to work in C, but I ran into 
problems with C++.

The following code;

auto t = std::chrono::system_clock::now();

does not seem to work correctly. When the system date is less than 2038 
it works and gives back the correct time, but for dates > 2038 it seems 
to return some 1970 date.

Conversion functions on the other hand seem to work;

auto t = std::chrono::system_clock::from_time_t(time(nullptr));

does a correct conversion of dates > 2038.

The defines like _TIME_BITS=64 are set correctly, and time_t is 64bit. 
Also calls like gettimeofday() works correctly.

Since the C++ std lib is part of the Toolchain, can it be that the 
Toolchain is not build correctly ?

Anybody any experience with y2038 in C++ on ptxdist ?

best regards,

Erwin



             reply	other threads:[~2024-05-23  6:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23  6:57 Erwin Rol [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2024-05-27 10:34             ` Christian Melki

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=4d22d190-aee5-4bb9-930d-dd78ecca593c@erwinrol.com \
    --to=mailinglists@erwinrol.com \
    --cc=ptxdist@pengutronix.de \
    /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