mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2024.11.1 released
Date: Thu, 13 Mar 2025 12:37:01 +0100	[thread overview]
Message-ID: <Z9LDXRcIf9KCn7is@pengutronix.de> (raw)
In-Reply-To: <31a14194-1c2f-4a41-ab27-40a3c439712e@mev.co.uk>

Hi,

On Thu, Mar 13, 2025 at 10:36:25AM +0000, Ian Abbott wrote:
> On 13/03/2025 08:47, Michael Olbrich wrote:
> > I'm happy to announce that I've just released OSELAS.Toolchain-2024.11.1.
> > 
> > This is a bugfix only release. There are no major update. The relevant
> > changes are:
> 
> I'm guessing that this won't have the 64-bit time_t support in 32-bit
> libstdc++ since it's a bugfix only release. Is that correct?

Correct. And to be honest, I'm not sure how I should handle this. I've been
digging some more and there is a lot of code like this:

#ifdef _GLIBCXX_USE_CLOCK_GETTIME_SYSCALL
      syscall(SYS_clock_gettime, CLOCK_REALTIME, &tp);
#else
      clock_gettime(CLOCK_REALTIME, &tp);
#endif

And the problem with that is, that -D_TIME_BITS=64 only works correctly if
clock_gettime() is used and not the syscall directly. And I'm not sure how
to guarantee that.
And so far, I've not really found any indication that gcc upstream is
actually working on that in any way.

So I don't know what I will do for the next major release. Just building
with -D_TIME_BITS=64 for the official toolchains is not something that I'm
comfortable with right now.
Maybe an option to enable it and keep it disabled by default? That way, you
could at least build the toolchain with it in a defined way.

Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2025-03-13 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13  8:47 Michael Olbrich
2025-03-13 10:36 ` Ian Abbott
2025-03-13 11:37   ` Michael Olbrich [this message]

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=Z9LDXRcIf9KCn7is@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --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