From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [committed][gdb/testsuite] Fix DUPLICATE in gdb.base/cvexpr.exp
Date: Thu, 30 Sep 2021 19:09:20 +0200 [thread overview]
Message-ID: <20210930170918.GA25046@delia> (raw)
Hi,
Fix:
...
DUPLICATE: gdb.base/cvexpr.exp: ptype int * restrict
...
using with_test_prefix.
Tested on x86_64-linux.
Committed to trunk.
Thanks,
- Tom
[gdb/testsuite] Fix DUPLICATE in gdb.base/cvexpr.exp
---
gdb/testsuite/gdb.base/cvexpr.exp | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/gdb/testsuite/gdb.base/cvexpr.exp b/gdb/testsuite/gdb.base/cvexpr.exp
index c434c11f45f..33ae1be0322 100644
--- a/gdb/testsuite/gdb.base/cvexpr.exp
+++ b/gdb/testsuite/gdb.base/cvexpr.exp
@@ -514,7 +514,9 @@ gdb_test "ptype int * restrict" "type = int \\* restrict"
# C++ does not have "restrict".
gdb_test_no_output "set lang c++"
-gdb_test "ptype int * restrict" "A syntax error in expression.*"
+with_test_prefix c++ {
+ gdb_test "ptype int * restrict" "A syntax error in expression.*"
-# There is a GCC extension for __restrict__, though.
-gdb_test "ptype int * __restrict__" "type = int \\* __restrict__"
+ # There is a GCC extension for __restrict__, though.
+ gdb_test "ptype int * __restrict__" "type = int \\* __restrict__"
+}
reply other threads:[~2021-09-30 17:10 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=20210930170918.GA25046@delia \
--to=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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