From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Revisiting 64-bit time_t
Date: Sat, 29 Jun 2019 12:21:16 -0400 [thread overview]
Message-ID: <20190629162116.GJ1506@brightrain.aerifal.cx> (raw)
In-Reply-To: <3424A001-EBF1-412E-B0F4-A7E834966807@adelielinux.org>
On Sat, Jun 29, 2019 at 03:36:19AM -0500, A. Wilcox wrote:
> Overall this seems like a decent proposal. However...
>
> On Jun 28, 2019, at 10:06 AM, Rich Felker <dalias@libc.org> wrote:
> > However Y2038 is not all that far off, desktop/server distros really
> > have rather little interest left in 32-bit archs (especially not
> > coordinating a costly ABI swap just for them)
>
> This is really incorrect. We at Adélie are QUITE interested in
> 32-bit architectures including:
>
> [...]
>
> Please, please do not write off 32-bit desktop usage.
I'm sorry my wording contributed to a narrative that 32-bit is dead;
that's not at all my intent, but I can see how it could be harmful to
efforts to maintain support.
My intent here is the other direction -- due to dominance of 64-bit
archs on desktop and server these days, there's much less effort being
put into the future of 32-bit ones, and I don't want to make a
decision here that would incentivize distros that don't already care
strongly about keeping 32-bit arch support to just drop it, rather
than going through a painful ABI swap-out.
Thanks for your work continuing to press applications not to break
these archs.
Rich
next prev parent reply other threads:[~2019-06-29 16:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 15:06 Rich Felker
2019-06-29 8:36 ` A. Wilcox
2019-06-29 16:21 ` Rich Felker [this message]
2019-07-01 14:41 ` Arnd Bergmann
2019-07-01 14:50 ` A. Wilcox
2019-07-01 15:41 ` Rich Felker
2019-07-01 15:55 ` A. Wilcox
2019-07-01 15:57 ` Florian Weimer
2019-07-01 16:07 ` Rich Felker
2019-07-02 9:35 ` Arnd Bergmann
2019-07-02 21:09 ` Rich Felker
2019-06-29 16:35 ` Rich Felker
2019-07-01 14:42 ` Arnd Bergmann
2019-07-01 15:31 ` Rich Felker
2019-07-01 21:12 ` Arnd Bergmann
2019-07-01 22:07 ` Rich Felker
2019-07-02 8:28 ` Arnd Bergmann
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=20190629162116.GJ1506@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).