public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb] Allow frv::fr300 in selftests Date: Tue, 7 Jun 2022 07:59:57 +0000 (GMT) [thread overview] Message-ID: <20220607075957.8B669384D166@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e97198fdcdb7c86c70b85a0746d7a7ab5c87bbdf commit e97198fdcdb7c86c70b85a0746d7a7ab5c87bbdf Author: Tom de Vries <tdevries@suse.de> Date: Tue Jun 7 09:59:54 2022 +0200 [gdb] Allow frv::fr300 in selftests In skip_arch in gdb/selftest-arch.c we skip architecture fr300 because of PR20946, but the PR has been fixed by commit 0ae60c3ef45 ("Prevent an abort in the FRV disassembler if the target bfd name is unknown.") in Januari 2017. Remove the skipping of frv::fr300. Tested on x86_64-linux. Diff: --- gdb/selftest-arch.c | 6 ------ 1 file changed, 6 deletions(-) diff --git a/gdb/selftest-arch.c b/gdb/selftest-arch.c index 33d7875c120..9e99098783e 100644 --- a/gdb/selftest-arch.c +++ b/gdb/selftest-arch.c @@ -28,12 +28,6 @@ namespace selftests { static bool skip_arch (const char *arch) { - if (strcmp ("fr300", arch) == 0) - { - /* PR 20946 */ - return true; - } - if (strcmp ("powerpc:EC603e", arch) == 0 || strcmp ("powerpc:e500mc", arch) == 0 || strcmp ("powerpc:e500mc64", arch) == 0
reply other threads:[~2022-06-07 7:59 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=20220607075957.8B669384D166@sourceware.org \ --to=vries@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).