From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Andrew Burgess <aburgess@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH 1/2] opcodes/mips: use .word/.short for undefined instructions
Date: Thu, 2 Feb 2023 09:48:10 +0000 (GMT) [thread overview]
Message-ID: <alpine.DEB.2.21.2302011938340.32532@angie.orcam.me.uk> (raw)
In-Reply-To: <875ycltn9f.fsf@redhat.com>
On Wed, 1 Feb 2023, Andrew Burgess wrote:
> > I'd say it's OK, except that I put your change through my MIPS regression
> > tester and that revealed failures from your new case for numerous
> > targets,
>
> Can you let me know which targets I should configure for to expose these
> failures, then I can ensure I've fully tested this before posting an
> update.
In this case those that I quoted as examples should do, e.g. `mips-elf'
and `mipsisa32r6-elf'. If you have a way to automate testing and would
prefer to use my full list of MIPS targets, then it is as follows:
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 shouldn't take too long on a reasonably modern machine (it takes less
than 0.5h on my development system to build and test all these).
Maciej
next prev parent reply other threads:[~2023-02-02 9:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 13:58 [PATCH 0/2] MIPS disassembler styling Andrew Burgess
2022-11-03 13:58 ` [PATCH 1/2] opcodes/mips: use .word/.short for undefined instructions Andrew Burgess
2023-01-06 15:58 ` Maciej W. Rozycki
2023-01-06 16:40 ` Andrew Burgess
2023-01-08 16:05 ` Maciej W. Rozycki
2023-01-17 10:28 ` Andrew Burgess
2023-01-27 11:57 ` Maciej W. Rozycki
2023-01-30 9:34 ` Andrew Burgess
2023-02-01 10:40 ` Maciej W. Rozycki
2023-02-01 15:32 ` Andrew Burgess
2023-02-02 9:48 ` Maciej W. Rozycki [this message]
2023-02-03 9:31 ` Andrew Burgess
2023-02-13 12:07 ` Andrew Burgess
2023-02-14 4:43 ` Maciej W. Rozycki
2022-11-03 13:58 ` [PATCH 2/2] libopcodes/mips: add support for disassembler styling Andrew Burgess
2022-11-28 17:15 ` [PATCH 0/2] MIPS " Andrew Burgess
2022-11-30 16:50 ` Nick Clifton
2022-12-05 10:08 ` Andrew Burgess
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.2302011938340.32532@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=aburgess@redhat.com \
--cc=binutils@sourceware.org \
/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).