Repository navigation
Conversation
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
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.
The riscv32 Linux ABI provides
futex_time64and has no legacy time32 futex syscall. With libc 0.2.190 or newer, compiling the thread APIs fails because the legacy fallback still references the removedSYS_futexconstant.Exclude that fallback on riscv32 and add its source-built target to the existing Tier 3 CI checks. Other 32-bit targets retain the ENOSYS fallback. Fixes #1729.
Validation: the riscv32 all-APIs check fails on current main and passes with this change; the minimal std/thread check passes too. Armv7 and i686 libc-backend checks, native all-targets checking and formatting pass. Both native thread suites pass 32 tests with two capability-dependent skips each. The requested full raw/libc suites stop at an existing test opening the unavailable
/dev/net/tun; the exact failure also occurs on clean main. Two existing unused-syscall-constant warnings remain in the riscv32 all-APIs check. No native riscv32 execution or older-kernel deployment was performed.