t; From
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_abe stage1:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 22321
> # linux build successful:
> all
This problem still reproduces on next-20240410, so I reported it to the
patch author. He re
Maxim Kuvyrkov writes:
> [CC: Thiago, for GDB crash]
Thanks!
> However, if I try to print "x", GDB crashes:
> ===
> (gdb) p x
> $2 = ( _data = (0x6568,
> /build/gdb-aPmCGS/gdb-12.1/gdb/value.c:856: internal-error:
> value_contents_bits_eq:
> Assertion `offset1 + length <= TYPE_LENGTH
[CC: Thiago, for GDB crash]
Hi Paul,
The test crashes immediately, it doesn't time out. You see "timeout" in the
output because we run all tests under "timeout" utility.
The backtrace is from the crash is:
===
rogram received signal SIGSEGV, Segmentation fault.
0xf7da9070 in arena_for_chunk
Hi there,
Thanks for the heads-up on gcc patch #88281: 6 regressions on arm.
I see from the log that the test timed-out and the core was dumped. I
cannot reproduce this and can see nothing in the tree-dump that might cause
a time out. I would appreciate some help on where the fault lies and what
