public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] sim: testsuite: fix cris badarch in multi-target builds Date: Thu, 3 Nov 2022 18:43:02 +0000 (GMT) [thread overview] Message-ID: <20221103184303.3AF2D385841B@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4ce3ba0865ee156be63c3d763f1678cbe57d7dd6 commit 4ce3ba0865ee156be63c3d763f1678cbe57d7dd6 Author: Mike Frysinger <vapier@gentoo.org> Date: Wed Nov 2 20:25:27 2022 +0545 sim: testsuite: fix cris badarch in multi-target builds This test assumes that /bin/sh will never be a CRIS ELF by way of assuming that the current bfd cannot load it (since a basic cris cross-compiler only understands CRIS ELFs). In a multi-target build though, bfd understands just about every ELF out there, so we're able to read the /bin/sh format before failing at a diff point in the cris code. Let's switch to using / instead since it'll fail for a similar reason (at least similar enough for what this test is testing). Diff: --- sim/testsuite/cris/asm/badarch1.ms | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sim/testsuite/cris/asm/badarch1.ms b/sim/testsuite/cris/asm/badarch1.ms index 3d0d8121834..c7f27390efa 100644 --- a/sim/testsuite/cris/asm/badarch1.ms +++ b/sim/testsuite/cris/asm/badarch1.ms @@ -1,5 +1,5 @@ # mach: crisv3 crisv8 crisv10 crisv32 # xerror: # output: *not a CRIS program* -# sim: /bin/sh +# sim: / .include "nopv32t.ms"
reply other threads:[~2022-11-03 18:43 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221103184303.3AF2D385841B@sourceware.org \ --to=vapier@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).