Update POSIX edition links#158505
Open
schneems wants to merge 2 commits into
Open
Conversation
Comments and doc links across std, core, and a process test referenced the older issue 7 (2018 edition) of the POSIX spec, with one link still on issue 6. Point them all at the current issue 8 (2024 edition, IEEE Std 1003.1-2024) under onlinepubs/9799919799, and normalize the `9799919799.2024edition` URL variant to the canonical path. Links that carry a section anchor were verified against the 2024 edition, since section numbering shifts between editions: - Pathname Resolution moved from 4.13 (tag_04_13) to 4.16 (tag_04_16) - Field Splitting moved from tag_18_06_05 to tag_19_06_05 - LC_CTYPE (tag_07_03_01) was unchanged CI's linkchecker only validates intra-doc links, not external URLs, so each page and anchor was checked by hand.
Update the remaining pubs.opengroup.org links in Miri's Unix shims from issue 7 (9699919799) to the current issue 8 / 2024 edition (9799919799). All are anchorless, so only the edition path changes.
Collaborator
|
cc @rust-lang/miri |
rustbot
added
O-unix
Collaborator
|
r? @Darksonn rustbot has assigned @Darksonn. Use Why was this reviewer chosen?The reviewer was selected based on:
|
RalfJung
reviewed
Jun 27, 2026
| @@ -714,7 +714,7 @@ trait EvalContextPrivExt<'tcx>: MiriInterpCxExt<'tcx> { | |||
| // "in the past" fire before any other thread can take an action. This ensures that for | |||
| // `pthread_cond_timedwait`, "an error is returned if [...] the absolute time specified by | |||
| // abstime has already been passed at the time of the call". | |||
| // <https://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_cond_timedwait.html> | |||
| // <https://pubs.opengroup.org/onlinepubs/9799919799/functions/pthread_cond_timedwait.html> | |||
Member
There was a problem hiding this comment.
Doesn't this risk causing a dangling reference since whatever quote or behavior the text was referring to might have gotten changed in the latest version?
Collaborator
|
A job failed! Check out the build log: (web) (plain enhanced) (plain) Click to see the possible cause of the failure (guessed by this bot) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Comments that reference https://pubs.opengroup.org point to issue 7 (the 2018 edition of IEEE Std 1003.1-2017), with one link still on the older issue 6. The latest issue is 8 (the 2024 edition, IEEE Std 1003.1-2024). From https://www.opengroup.org/austin/papers/posix_faq.html:
Issue 8 lives at https://pubs.opengroup.org/onlinepubs/9799919799/.
This PR points all older-edition links to issue 8.
Most links are a straight edition bump, but links with a section anchor needed their anchor rechecked, because section numbering shifts between editions. Verified against the 2024 edition:
tag_04_13) to 4.16 (tag_04_16)tag_18_06_05totag_19_06_05tag_07_03_01) was unchangedThe Miri changes (
src/tools/miri/) are kept in a separate commit since that's a synced subtree. I'm happy to move them to arust-lang/miriPR if preferred.