public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Use require using_fission Date: Fri, 13 Jan 2023 20:37:34 +0000 (GMT) [thread overview] Message-ID: <20230113203734.5601938543BE@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a231b2322f8d8f1978a2e9c8c0dea006aa578802 commit a231b2322f8d8f1978a2e9c8c0dea006aa578802 Author: Tom Tromey <tom@tromey.com> Date: Thu Dec 15 16:51:08 2022 -0700 Use require using_fission This changes some tests to use "require using_fission". Diff: --- gdb/testsuite/gdb.base/info-macros.exp | 5 +---- gdb/testsuite/gdb.linespec/macro-relative.exp | 5 +---- 2 files changed, 2 insertions(+), 8 deletions(-) diff --git a/gdb/testsuite/gdb.base/info-macros.exp b/gdb/testsuite/gdb.base/info-macros.exp index 803e026ae3a..38eb35f1df8 100644 --- a/gdb/testsuite/gdb.base/info-macros.exp +++ b/gdb/testsuite/gdb.base/info-macros.exp @@ -16,10 +16,7 @@ standard_testfile .c # Fission doesn't support macros yet. Bug 15954. -if [using_fission] { - untested "fission does not support macros yet" - return -1 -} +require !using_fission if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile} {debug macros}] } { return -1 diff --git a/gdb/testsuite/gdb.linespec/macro-relative.exp b/gdb/testsuite/gdb.linespec/macro-relative.exp index d0e2cdae1d8..41159431ddc 100644 --- a/gdb/testsuite/gdb.linespec/macro-relative.exp +++ b/gdb/testsuite/gdb.linespec/macro-relative.exp @@ -16,10 +16,7 @@ standard_testfile # Fission doesn't support macros yet. Bug 15954. -if [using_fission] { - unsupported "fission" - return -1 -} +require !using_fission if [is_remote host] { unsupported "compiling on a remote host does not support a filename with directory."
reply other threads:[~2023-01-13 20:37 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=20230113203734.5601938543BE@sourceware.org \ --to=tromey@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).