public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Alan Modra <amodra@gmail.com>
Cc: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: New failures for the mips64el-openbsd target
Date: Fri, 16 Jun 2023 15:07:14 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2306161322290.64925@angie.orcam.me.uk> (raw)
In-Reply-To: <ZIvlGrun4sd98bDO@squeak.grove.modra.org>

On Fri, 16 Jun 2023, Alan Modra wrote:

> >  It may well be that one of the YunQiang Su's patches I have reverted 
> > brough these back; a regression from his earlier commit(s) anyway.
> 
> Hi Maciej,
> The testsuite fixes that you've reverted were not just fixing
> regressions from earlier commits.

 I was aware there could be fallout from the revert, especially as there 
was a conflict with a change of yours in a generic test case, which I 
resolved by only leaving your change in.  This is an unfortunate 
consequence of having unrelated changes bundled together in the original 
commit.

> >  I think let's wait and see how YunQiang handles it,
> 
> Can I suggest you post a list of mips targets you'd like to be
> regression tested with any mips specific changes?
> 
> FWIW, I test mips-linux-gnu, mips-sgi-irix6, mips-vxworks,
> mips64-linux-gnuabi64, mips64-openbsd, mips64el-openbsd,
> mipsel-linux-gnu, mipsisa32el-linux-gnu, mipsisa32r2el-elf, and
> mipstx39-elf as part of the set of targets that I check regularly in
> order to stop me breaking everything.  I also have a full cross
> toolchain installed for mips64-linux-gnuabi64 and mips-linux-gnu.
> Even that limited set showed problems with YunQiang Su's patches.

 Here's my current set of MIPS targets:

mips-elf mips-img-elf mips-mti-elf mips-sde-elf mips-freebsd 
mips-sgi-irix5 mips-sgi-irix6 mips-kfreebsd-gnu mips-linux mips-img-linux 
mips-mti-linux mips-netbsd mips-rtems mips-vxworks mips-windiss 
mips64-freebsd mips64-kfreebsd-gnu mips64-linux mips64-img-linux 
mips64-mti-linux mips64-openbsd mips64el-ps2-elf mips64el-freebsd 
mips64el-kfreebsd-gnu mips64el-linux mips64el-img-linux mips64el-mti-linux 
mips64el-openbsd mips64vr-elf mips64vr4300-elf mips64vr4300el-elf 
mips64vrel-elf mipsel-elf mipsel-img-elf mipsel-mti-elf mipsel-ps2-elf 
mipsel-sde-elf mipsel-freebsd mipsel-kfreebsd-gnu mipsel-linux 
mipsel-img-linux mipsel-mti-linux mipsel-netbsd mipsel-vxworks 
mipsisa32-elf mipsisa32-linux mipsisa32el-elf mipsisa32el-linux 
mipsisa32r2-elf mipsisa32r2-linux mipsisa32r2el-elf mipsisa32r2el-linux 
mipsisa32r3-elf mipsisa32r3-linux mipsisa32r3el-elf mipsisa32r3el-linux 
mipsisa32r5-elf mipsisa32r5-linux mipsisa32r5el-elf mipsisa32r5el-linux 
mipsisa32r6-elf mipsisa32r6-linux mipsisa32r6el-elf mipsisa32r6el-linux 
mipsisa64-elf mipsisa64-linux mipsisa64el-elf mipsisa64el-linux 
mipsisa64r2-elf mipsisa64r2-linux mipsisa64r2el-elf mipsisa64r2el-linux 
mipsisa64r3-elf mipsisa64r3-linux mipsisa64r3el-elf mipsisa64r3el-linux 
mipsisa64r5-elf mipsisa64r5-linux mipsisa64r5el-elf mipsisa64r5el-linux 
mipsisa64r6-elf mipsisa64r6-linux mipsisa64r6el-elf mipsisa64r6el-linux 
mipsr5900el-elf mipsr5900el-linux tx39-elf

It takes ~20 minutes to verify them all, so not a big deal.

 I'm mostly not set up for verifying compiled tests and I think it would
be infeasible to maintain such a huge number of cross-toolchains (some of 
which I have no access to suitable runtime to).  I remember quirks related 
to PLT vs SVR4 configurations affecting some of those tests.  Overall it 
would be good to get that part cleaned up, but it seems like many engineer 
hours' worth of effort.

 We had discussions on compiled tests before and my conclusion is they're 
really a compromise for the lack of resources to have them implemented as 
individual assembled tests across all the relevant targets.

> Meanwhile, I'm going to correct the ld-elf/eh5 test for hppa64.

 Thank you.  This is indeed the file that conflicted.

 For the record here's my list of non-MIPS targets I use for verification:

aarch64-elf aarch64-linux alpha-dec-vms alpha-linux alpha-linuxecoff 
alpha-netbsd alpha-unknown-freebsd4.7 alpha-unknown-osf4.0 am33_2.0-linux 
arc-elf arc-linux arm-eabi arm-linuxeabi arm-netbsdelf arm-nto arm-pe 
arm-vxworks arm-wince-pe avr-elf bfin-elf bfin-uclinux bpf cr16-elf 
cris-elf crisv32-linux crx-elf csky-elf csky-linux d10v-elf d30v-elf 
dlx-elf fr30-elf frv-elf frv-linux ft32-elf h8300-elf hppa-linux 
hppa-hp-hpux10 hppa64-hp-hpux11.23 hppa64-linux i386-bsd i386-darwin 
i386-linux i386-lynxos i386-msdos i586-linux i686-pc-beos i686-pc-elf 
i686-pe ia64-elf ia64-freebsd5 ia64-hpux ia64-linux ia64-netbsd ia64-vms 
ip2k-elf iq2000-elf lm32-elf m32c-elf m32r-elf m68hc11-elf m68hc12-elf 
m68k-elf m68k-linux m68k-netbsdelf mcore-elf mcore-pe mep-elf metag-elf 
metag-linux microblaze-elf mmix mn10200-elf mn10300-elf mn10300-linux 
moxie-elf ms1-elf msp430-elf nds32be-linux nds32le-linux nios2-linux 
or1k-elf pdp11-dec-aout pj-elf powerpc-beos powerpc-eabisim 
powerpc-ibm-aix5.2.0 powerpc-linux powerpc-nto powerpc-wrs-vxworks 
powerpc64-linux powerpc64le-linux pru-elf riscv32-elf riscv32-linux 
riscv64-elf riscv64-linux rs6000-aix4.3.3 rs6000-aix5.1 rx-elf rx-linux 
s12z-elf s390-linux s390x-linux score-elf sh-elf sh-linux sh-nto sh-pe 
sh-rtems shl-unknown-netbsdelf sparc-linux sparc64-linux spu-elf 
tic30-unknown-coff tic4x-coff tic54x-coff tic6x-elf tic6x-uclinux 
tilegx-linux tilepro-elf v850-elf vax-linux vax-netbsdelf visium-elf 
wasm32 x86_64-elf x86_64-linux x86_64-mingw32 x86_64-solaris2 
xstormy16-elf xtensa-elf z80-coff z80-elf z8k-coff

I tend to update the list with new additions as I remember it every so 
often (I haven't on this occasion) and of course remove obsoleted targets 
as they fail to configure.  Right now ia64-* targets do not build due to a 
GCC warning in GAS.  Then numerous targets have no support in gprofng, so 
I have disabled this tool in configuration.

  Maciej

      reply	other threads:[~2023-06-16 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 10:46 Nick Clifton
2023-06-15 14:43 ` Maciej W. Rozycki
2023-06-16  3:00   ` YunQiang Su
2023-06-16 13:33     ` Maciej W. Rozycki
2023-06-19  7:12       ` YunQiang Su
2023-06-19  7:23       ` YunQiang Su
2023-06-16  4:29   ` Alan Modra
2023-06-16 14:07     ` Maciej W. Rozycki [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.2306161322290.64925@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).