From: Florian Weimer <fweimer@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Paul Eggert <eggert@cs.ucla.edu>, Rich Felker <dalias@libc.org>,
GNU C Library development <libc-alpha@sourceware.org>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH v2] linux: Use 'long int' for timespec tv_nsec on x32 (BZ #16437)
Date: Sat, 11 Dec 2021 13:51:21 +0100 [thread overview]
Message-ID: <87ilvv2tkm.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAK8P3a3uPsM13zqoP80Pq9h+LHtp14MxRyY7mRN1D9mj-0XrSg@mail.gmail.com> (Arnd Bergmann's message of "Sat, 11 Dec 2021 12:26:21 +0100")
* Arnd Bergmann:
> On Sat, Dec 11, 2021 at 1:47 AM Paul Eggert <eggert@cs.ucla.edu> wrote:
>> On 12/10/21 16:08, Rich Felker wrote:
>> > this is a bug fix for a serious conformance problem
>> > that's going to have people writing wacky code to work around x32
>>
>> In my experience it's not a significant conformance issue. I've had very
>> little trouble writing user code that's portable to x32 struct timespec.
>> Generally speaking the code just works anyway; in the few cases where
>> there might have been trouble the fixes were trivial and non-wacky.
>>
>> Anybody writing portable struct timespec code has more important
>> problems than this (e.g., Solaris 11 'stat' can set st_mtim.tv_nsec to a
>> negative integer, something that's caused me far more hassle). And
>> anybody porting to x32 has waaaaayy more important problems than this.
>>
>> > if anyone even actually cares about x32
>>
>> If the x32 user community (small as it is) doesn't care about this issue
>> then we all have better things to do than worry about it.
>
> Would it help to resume the thread about removing the kernel support,
> followed by removing glibc support? The last time Andy brought this up
> was three years ago[1], and it was borderline then with about five users
> saying they actually used it at the time and several kernel developers
> speaking out in favor of removing the kernel bits.
>
> The timing probably isn't bad either, with Debian 11 and Ubuntu 22.04
> (both of which include marginal support for x32) being supported for
> years to come. Anyone building their own stuff can rely on linux-5.15lts
> and an existing glibc release to do the same.
I don't see x86-64 x32 causing us significant trouble on the glibc side.
I have worked on some x86-64-specific enhancements, and covering both
word sizes wasn't too hard because everything else is so similar. But I
am very emphatically not an x32 user.
Much higher on my annoyance list are alpha, hppa, ia64.
Thanks,
Florian
next prev parent reply other threads:[~2021-12-11 12:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 11:02 Adhemerval Zanella
2021-12-10 15:36 ` H.J. Lu
2021-12-10 15:44 ` Florian Weimer
2021-12-10 19:28 ` Adhemerval Zanella
2021-12-11 0:08 ` Rich Felker
2021-12-11 0:47 ` Paul Eggert
2021-12-11 11:26 ` Arnd Bergmann
2021-12-11 12:51 ` Florian Weimer [this message]
2021-12-11 16:32 ` Arnd Bergmann
2021-12-11 14:49 ` Rich Felker
2021-12-11 22:30 ` Arnd Bergmann
2021-12-11 18:50 ` Florian Weimer
2021-12-11 19:22 ` Andreas Schwab
2021-12-11 20:33 ` Rich Felker
2021-12-11 20:57 ` Andreas Schwab
2021-12-10 15:47 ` Adhemerval Zanella
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=87ilvv2tkm.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
--cc=luto@kernel.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).