☠ Buildbot (Sourceware): binutils-gdb - failed test (failure) (master)

[Alan Modra]

On Sun, Sep 28, 2025 at 10:51:46AM +0100, Nick Alcock wrote:
> On 25 Sep 2025, Alan Modra said:
> > I see the following with the cross-compilers I have installed.
> >
> > aarch64-linux-gnu  +FAIL: libctf-lookup/multidim-array
> > alpha-linux-gnu  +FAIL: libctf-lookup/multidim-array
> > arm-linux-gnueabi  +FAIL: libctf-lookup/multidim-array
> > hppa-linux-gnu  +FAIL: libctf-lookup/multidim-array
> > ia64-linux-gnu  +FAIL: libctf-lookup/multidim-array
> > m68k-linux-gnu  +FAIL: libctf-lookup/multidim-array
> > microblaze-linux-gnu  +FAIL: libctf-lookup/multidim-array
> > mips64-linux-gnuabi64  +FAIL: libctf-lookup/multidim-array
> > mips-linux-gnu  +FAIL: libctf-lookup/multidim-array
> > powerpc-linux-gnu  +FAIL: libctf-lookup/multidim-array
> > riscv64-linux-gnu  +FAIL: libctf-lookup/multidim-array
> > s390-linux-gnu  +FAIL: libctf-lookup/multidim-array
> > s390x-linux-gnu  +FAIL: libctf-lookup/multidim-array
> > sh4-linux-gnu  +FAIL: libctf-lookup/multidim-array
> > sparc64-linux-gnu  +FAIL: libctf-lookup/multidim-array
> 
> What versions are these compilers?

They are all "13.0.0 20220910 (experimental)"

> 
> > Using an older version of gcc should not result in a FAIL.  We are
> > testing binutils here, not gcc.  
> 
> Indeed not
> 
> > The following works for me, but I'll leave this to you to commit
> > since I have no idea about which versions of gcc we should be
> > checking.  The test gets more complicated if bug fixes are backported.
> 
> That shouldn't be necessary. We have three cases here:
> 
>  - older GCC (pre-14.2.0): GCC dumps array dimensions backwards
>    (whoops), libctf detects this and prints them backwards too, so at
>    least type printing is still correct, even if type graph traversal is
>    broken.
> 
>  - GCC post-14.2.0: dumps array dimensions the right way round, without
>    header flag indicating that they are backwards; the test endeavours
>    to detect this with a type graph traversal (and a dump to check for
>    the flag) and go UNSUPPORTED rather than failing.
> 
>  - GCC emitting the header flag (not yet pushed): the test runs
>    properly, checking that the dumped order is right.
> 
> If the first of these cases isn't working, we have a bug, and given that
> at least half of my test matrix was against such older compilers (in the
> compile farm and locally), I'd like to know why the buildbot tests are
> failing when all my tests worked...

Ah, OK, I also might have fooled the detection logic by building my
own set of compilers based on mainline gcc sources.

-- 
Alan Modra