From: Paul Eggert <eggert@cs.ucla.edu>
To: libc-coord@lists.openwall.com, Rich Felker <dalias@libc.org>
Cc: linux-man@vger.kernel.org, musl@lists.openwall.com,
libc-alpha@sourceware.org
Subject: [musl] Re: [libc-coord] Re: [musl] Re: regression in man pages for interfaces using loff_t
Date: Sat, 1 Jul 2023 00:24:27 -0700 [thread overview]
Message-ID: <f3f58057-f764-b4bf-a3fe-92867cfa3131@cs.ucla.edu> (raw)
In-Reply-To: <20230630233705.GW4163@brightrain.aerifal.cx>
On 2023-06-30 16:37, Rich Felker wrote:
> glibc made it so off_t can be 32- or 64-bit depending on
> _FILE_OFFSET_BITS, and if it's 32-bit, there is no matching version of
> the libc syscall wrappers for these functions. It seems to have been a
> conscious choice not to make any.
Yes, _FILE_OFFSET_BITS=32 is obsolescent. Among other things in
GNU/Linux it is guaranteed to stop working in the year 2038, because you
can't have 64-bit time_t without also having 64-bit off_t. There is no
interest in supporting _FILE_OFFSET_BITS=32 for new APIs, which these are.
> I'm talking about
> how an interface using a type that's under somebody else's
> jurisdiction
I don't understand why jurisdiction matters here. Although off_t is
under someone else's (POSIX's) jurisdiction, that doesn't mean the Linux
man pages can't use POSIX-specified types like off_t.
> This is still changing the documentated signature, which isn't really
> nice, and would not be compatible with glibc unless glibc went out of
> its way to hide those functions when _FILE_OFFSET_BITS is 32.
I don't see any incompatibility with glibc and the changes I proposed.
The changes merely weaken the spec in the man pages in an area where the
spec should be weakened. glibc is compatible with the spec before it was
changed to use off64_t, it's compatible with the spec now that it uses
off64_t, and it would continue to be compatible with the spec if the
proposed changes are adopted.
next prev parent reply other threads:[~2023-07-01 7:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 17:53 [musl] " Rich Felker
2023-06-28 18:21 ` [musl] " Paul Eggert
2023-06-28 19:15 ` Rich Felker
2023-06-30 7:11 ` Paul Eggert
2023-06-30 8:02 ` [musl] Re: [libc-coord] " Jonathan Wakely
2023-06-30 8:14 ` Jonathan Wakely
2023-06-30 8:30 ` Sam James
2023-06-30 19:44 ` Paul Eggert
2023-07-02 1:18 ` A. Wilcox
2023-07-02 19:21 ` Paul Eggert
2023-07-03 18:16 ` Jakub Wilk
2023-07-03 21:35 ` Paul Eggert
2023-07-08 17:03 ` Alejandro Colomar
2023-07-09 6:07 ` [musl] [PATCH v4] off64_t: prefer off_t for splice, etc Paul Eggert
2023-07-09 6:16 ` [musl] Re: [libc-coord] " Sam James
2023-07-15 15:08 ` Alejandro Colomar
2023-07-15 18:35 ` Rich Felker
2023-07-15 20:01 ` Paul Eggert
2023-07-16 0:35 ` Alejandro Colomar
2023-07-16 0:39 ` Alejandro Colomar
2023-06-30 23:37 ` [musl] Re: regression in man pages for interfaces using loff_t Rich Felker
2023-07-01 7:24 ` Paul Eggert [this message]
2023-07-01 13:36 ` [musl] Re: [libc-coord] " Szabolcs Nagy
2023-07-01 23:02 ` Paul Eggert
2023-07-01 14:32 ` Rich Felker
2023-07-01 18:45 ` Alejandro Colomar
2023-07-01 23:06 ` Paul Eggert
2023-06-28 19:19 ` Szabolcs Nagy
2023-06-28 19:28 ` Rich Felker
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=f3f58057-f764-b4bf-a3fe-92867cfa3131@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=dalias@libc.org \
--cc=libc-alpha@sourceware.org \
--cc=libc-coord@lists.openwall.com \
--cc=linux-man@vger.kernel.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).