Workaround known failures (May 24, 2025) #834
Merged
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
allyesconfig has grown too large to link due to KASAN being enabled
after commit 6f110a5e4f99 ("Disable SLUB_TINY for build testing").
Signed-off-by: Nathan Chancellor <[email protected]>
Link: https://lore.kernel.org/20250317174840.GA1451320@ax162/ Signed-off-by: Nathan Chancellor <[email protected]>
A recent backport exposed Hexagon's lack of readsb() in 5.15. This is resolved in mainline by switching to the generic IO accessors but backporting this is not the cleanest due to the HAS_IOPORT rework that happened gradually over time. As Hexagon is already a relatively low priority target and it is happening in an older LTS release, just disable the build. If others notice and truly care, we can explore addressing this properly at the source level. Signed-off-by: Nathan Chancellor <[email protected]>
On mainline and -next, which contain commit 56651128e2fb ("MIPS: Fix
idle VS timer enqueue"), builds older than clang-nightly (21.0.0) fail
with:
<instantiation>:7:11: error: expected an immediate
ori $26, r4k_wait_idle_size - 2
^
<instantiation>:10:13: error: expected an immediate
addiu $26, r4k_wait_exit - r4k_wait_insn + 2
^
<instantiation>:10:29: error: expected an immediate
addiu $26, r4k_wait_exit - r4k_wait_insn + 2
^
<instantiation>:7:11: error: expected an immediate
ori $26, r4k_wait_idle_size - 2
^
<instantiation>:10:13: error: expected an immediate
addiu $26, r4k_wait_exit - r4k_wait_insn + 2
^
<instantiation>:10:29: error: expected an immediate
addiu $26, r4k_wait_exit - r4k_wait_insn + 2
^
This was fixed tangentially in LLVM main. Switch to GNU binutils to
retain as much LLVM coverage as possible.
Link: llvm/llvm-project@b65e094
Link: https://lore.kernel.org/[email protected]/
Signed-off-by: Nathan Chancellor <[email protected]>
Signed-off-by: Nathan Chancellor <[email protected]>
nathanchance
requested review from
JustinStitt,
bwendling and
nickdesaulniers
as code owners
JustinStitt
approved these changes
May 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This series disables or tweaks several builds that broken recently. See the individual changes for the full details. I plan to merge this immediately to try and make the matrix mostly green but I am happy to address anything in post-commit review.