From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: Michael Hudson-Doyle <michael.hudson@canonical.com>,
Sam James via Libc-alpha <libc-alpha@sourceware.org>,
Sam James <sam@gentoo.org>
Subject: Re: time64 / Large File Support: 2) default time64 breaks legacy 32bit binaries
Date: Fri, 03 Feb 2023 19:56:29 +0100 [thread overview]
Message-ID: <87ilgih92a.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <b5edea35-aa68-7ad7-ac51-a56ac35fa8c5@linaro.org> (Adhemerval Zanella Netto's message of "Fri, 3 Feb 2023 11:17:24 -0300")
* Adhemerval Zanella Netto:
> It is an option, although I am not sure what might really work since afaik
> Linux does not support CLOCK_REALTIME on time namespace.
Not yet. The pressure isn't there yet, but I totally see it happening.
> Not really, there are some idea on how to proceed with 64 time_t promotion:
>
> 1. Add a configure option to enable LFS and 64 bit time_t support as default.
> It is basically promoting the port to a new ABI, although a program can
> still build with non LFS or 32 bit time_t by explicit use -D_TIME_BITS=32.
>
> 2. Make this option the default on a future glibc version, meaning that for
> distribution that want to keep the the compatibility mode as default (to
> run old binaries) will need to explicit enable it.
>
> 3. Move the non-LFS and 32 bit time_t symbols compat one, meaning that newer
> binaries won't be able to use them and -D_TIME_BITS=32 won't be supported
> or just be a no-op.
>
> The 1 and 2 should not be cause many trouble, even if 2 would make
> 32-bit time_t opt-in. At least it would focused on glibc itself,
> meaning that a distribution could just ignore the transition by just
> adding a configure option on glibc build.
I tend to agree, except we'd have to make it clear that 1 (if enabled)
& 2 may require extensive porting work across the distribution to
maintain a consistent ABI.
> The 3. is what might cause i386 (and any 32-bit port where ABI also supports
> 64-bit) to wither. I don't have a strong opinion, maybe we should focus on
> only the 1. and 2. and see what community things about 3.
This still doesn't solve the implicit function declaration/dlsym
problem, though, so I don't know how
Meanwhile, Ocaml has removed compiler (but not interpreter) support for
i386, and Openblas dropped 32-bit support completely. I think it's
going to become more and more difficult to offer a general-purpose
distribution on i386 well before we hit Y2038 problems.
Thanks,
Florian
next prev parent reply other threads:[~2023-02-03 18:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 23:57 The time64 and Large File Support mess Andreas K. Huettel
2023-01-25 23:58 ` time64 / Large File Support: 1) [2.28 Regression]: New getdents{64} implementation breaks qemu-user Andreas K. Huettel
2023-01-26 12:21 ` Adhemerval Zanella Netto
2023-01-27 20:08 ` Andreas K. Huettel
2023-01-25 23:59 ` time64 / Large File Support: 2) default time64 breaks legacy 32bit binaries Andreas K. Huettel
2023-01-26 4:13 ` Paul Eggert
2023-01-26 13:21 ` Adhemerval Zanella Netto
2023-01-26 23:35 ` Sam James
2023-01-27 17:33 ` Adhemerval Zanella Netto
2023-02-01 16:26 ` Florian Weimer
2023-02-01 19:47 ` Sam James
2023-02-01 19:54 ` Sam James
2023-02-03 17:52 ` Florian Weimer
2023-02-01 22:22 ` Michael Hudson-Doyle
2023-02-03 14:17 ` Adhemerval Zanella Netto
2023-02-03 18:56 ` Florian Weimer [this message]
2023-01-27 2:38 ` Paul Eggert
2023-01-27 17:40 ` Adhemerval Zanella Netto
2023-01-27 23:51 ` Paul Eggert
2023-01-27 23:58 ` Joseph Myers
2023-02-01 12:27 ` Adhemerval Zanella Netto
2023-01-26 10:43 ` Florian Weimer
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=87ilgih92a.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=michael.hudson@canonical.com \
--cc=sam@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).