src/runtime/crash_unix_test.go | 4 4 + 0 - 0 !
1 file changed, 4 insertions(+)

 skip flaky testcrashdumpsallthreads on mips64le

crash_unix_test.go:145: found 3 instances of main.crashDumpsAllThreadsLoop; expected 4

src/runtime/crash_unix_test.go | 4 4 + 0 - 0 !
1 file changed, 4 insertions(+)

 skip flaky testcrashdumpsallthreads on s390x

Bug: https://github.com/golang/go/issues/64650

src/cmd/cgo/internal/testsanitizers/cshared_test.go | 3 3 + 0 - 0 !
src/cmd/cgo/internal/testsanitizers/tsan_test.go | 4 4 + 0 - 0 !
2 files changed, 7 insertions(+)

 skip tsan tests on riscv64
 Race detector on riscv64 is not support yet, this is usually no problem on Debian
 building because it will be skipped automatically. But others package updated
 recently lead to the test failed.

src/cmd/link/internal/loadelf/ldelf.go | 2 1 + 1 - 0 !
src/cmd/link/internal/loader/loader.go | 8 0 + 8 - 0 !
2 files changed, 1 insertion(+), 9 deletions(-)

 [patch] [release-branch.go1.24] cmd/link: fix cgo on riscv64 when
 building with gcc-15

It's not currently possible to build cgo programs that are partially
compiled with gcc-15 on riscv64 using the internal linker. There are
two reasons for this.

1. When gcc-15 compiles _cgo_export.c, which contains no actual code,
   for a riscv64 target, it emits a label in the .text section called
   .Letext0. This label is referred to by another section, .debug_line,
   and an entry is generated in the symbol table for it. The Go linker
   panics when processing the .Letext0 symbol in _cgo_export.o, as it
   occurs in an empty section.
2. GCC-15 is generating additional debug symbols with the .LVUS
   prefix, e.g., .LVUS33, that need to be ignored.

We fix the issue by removing the check in
cmd/link/internal/loader/loader.go that panics if we encounter a
symbol in an empty section (the comments preceding this check suggest
it's safe to remove it) and by adding .LVUS to the list of symbol
prefixes to ignore.

For #72840
Fixes #75351