riscv64-absolute-symbols fails with GCC 14

Question

marxin opened this issue 4 months ago · 9 comments

It started to fail on around August 31, though it might have been caused by a change in the GCC 14 compiler. The binary does not produce any output:

[ 5308s] + out/test/riscv64/absolute-symbols/exe
[ 5308s] + out/test/riscv64/absolute-symbols/exe
[ 5308s] + grep -q '^ip=0x80000.$'

No.

Answer 1 · 2024-09-05T10:30:03.000Z

When I ran your executable in a riscv64/ubuntu docker image, it printed out ip=0x800008. So it looks like it's system-dependent?

Answer 2 · 2024-09-05T11:06:42.000Z

Maybe. @andreas-schwab can help us, I guess?

Answer 3 · 2024-09-10T08:28:31.000Z

It's a qemu bug.

Answer 4 · 2024-09-10T09:30:54.000Z

Did you have a link to the qemu bug?

Answer 5 · 2024-09-10T10:17:18.000Z

How did you know it was a qemu bug?

Answer 6 · 2024-09-10T10:24:57.000Z

$ qemu-riscv64 ./exe
mmap stack: Cannot allocate memory

Answer 7 · 2024-09-10T11:09:59.000Z

@andreas-schwab Can you file an issue so that upstream knows about it?

Answer 8 · 2024-09-10T13:39:59.000Z

        0x7ee000           0x866000    0x78000        0x0  rw-p   [heap]