From: Joseph Myers <joseph@codesourcery.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
<libc-alpha@sourceware.org>
Subject: Re: time64 / Large File Support: 2) default time64 breaks legacy 32bit binaries
Date: Fri, 27 Jan 2023 23:58:04 +0000 [thread overview]
Message-ID: <8f7236db-a07d-3fd0-1cc-ee82519061b@codesourcery.com> (raw)
In-Reply-To: <bdebdf77-e0c1-503a-28c7-2d8029f5f1fe@cs.ucla.edu>
On Fri, 27 Jan 2023, Paul Eggert wrote:
> On 2023-01-27 09:40, Adhemerval Zanella Netto wrote:
> > > Another possibility is to adopt the milder approach for glibc version N,
> > > and switch to the more drastic approach in glibc version N+1.This would
> > > give distros time to test this new configure-time option before it's the
> > > default.
> > Do you mean add the --enable-hard-sys-types64 on glibc N, and then remove it
> > on
> > N+1 and make the 64-bit the default?
>
> Sure, that would work. If that's too fast we could do something more gradual,
> like this:
>
> 1. glibc version N supports --enable-hard-sys-types64 and
> --disable-hard-sys-types64 and the default is disabled.
>
> 2. glibc version N+1 is the same, but the default is enabled.
>
> 3. glibc version N+2 removes support for --disable-hard-sys-types64;
> --enable-hard-sys-type64 remains as a no-op.
One release is an extremely short time period for glibc (six months). A
few years between steps would seem better for something like this.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-01-27 23:58 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
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 [this message]
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=8f7236db-a07d-3fd0-1cc-ee82519061b@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.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).