Source: libstdc++-riscv64-unknown-elf Version: 5 Severity: important X-Debbugs-Cc: pkg-qemu-de...@lists.alioth.debian.org
See, for example, https://ci.debian.net/packages/libs/libstdc++-riscv64-unknown-elf/testing/amd64/60220610/ (or from current qemu package tracking page, https://tracker.debian.org/pkg/qemu). The relevant part is: riscv64-unknown-elf-g++ -specs=picolibcpp.specs --oslib=semihost -Os -march=rv32imac -mabi=ilp32 -Triscv-cpp.ld -Wl,-Map=hello-worldpp-riscv.map -o hello-worldpp-riscv.elf hello-worldpp.cpp /usr/lib/gcc/riscv64-unknown-elf/14.2.0/../../../riscv64-unknown-elf/bin/ld: warning: hello-worldpp-riscv.elf has a LOAD segment with RWX permissions ./run-riscv hello-worldpp-riscv.elf | cmp - ./expected-output qemu-system-riscv32: H extension implicitly requires S-mode I've no idea how this worked before, - maybe a toolchain difference, - dunno. The thing is that this part hasn't changed in qemu for quite some time, it's the same in bookworm qemu and earlier. It should've been failing before libstdc++-riscv64-unknown-elf migrated to testing, but it looks like it didn't. Right now this issue prevents migration of qemu to testing, which is important for trixie. Can you take a look please? Thanks, /mjt
