public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: gentoo-dev@lists.gentoo.org, toolchain@gentoo.org
Subject: Re: [gentoo-dev] time64 ABI fix coming to upstream glibc
Date: Fri, 03 May 2024 05:36:19 +0100	[thread overview]
Message-ID: <87ikzvldfg.fsf@gentoo.org> (raw)
In-Reply-To: <875xvwmrfq.fsf@oldenburg.str.redhat.com> (Florian Weimer's message of "Thu, 02 May 2024 12:36:09 +0200")

Florian Weimer <fweimer@redhat.com> writes:

> The <utmp.h> and <utmp.h> headers had a bug that the on-disk structures
> defined there could change size on some targets when _TIME_BITS was set
> to 64.  This is obviously wrong because the files are not going to
> magically change their layout because the application accessing them was
> built in a specific way.  We're going to fix this in glibc upstream on
> the stable release branches, going all the way back to glibc 3.34 (the
> first release with this kind of time64 support).  After the fix, the
> _TIME_BITS definition will no longer impact struct layout.  Usually,
> that means epoch fields are 32-bits wide, to match co-installable
> architectures.
>
> To extend the usable life-time of these interfaces somewhat, glibc 2.40
> changes epoch fields to unsigned types in these structures.  This change
> is specific to the upcoming glibc 2.40 release, I do not plan to
> backport it.

Thank you for the heads-up Florian. We haven't yet started our time64
migration - the plan is to start playing with it over the next few
months, so the timing has worked out well for us. We'll make sure the
fixes are pulled in before we solidify anything beyond experiments.

I'm trying not to wait *too* late to start, just in case we do end up
finding any other problems like this, rather than finding them years
down the line when it's too late to fix anything.

>
> Thanks,
> Florian

thanks,
sam


      reply	other threads:[~2024-05-03  4:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 10:36 [gentoo-dev] time64 ABI fix coming to upstream glibc Florian Weimer
2024-05-03  4:36 ` Sam James [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=87ikzvldfg.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=fweimer@redhat.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=toolchain@gentoo.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