From: Jason Merrill <jason@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] Adjust C++ destructor type tests
Date: Fri, 10 May 2024 16:33:20 -0400 [thread overview]
Message-ID: <20240510203409.1897598-1-jason@redhat.com> (raw)
In gcc-15-95-ga12cae97390 I dropped the unnecessary artificial "in-charge"
parameter from destructors of classes with no virtual bases; Linaro's CI
informed me that the gdb testsuite needs to be adjusted to match.
Teested against GCC 13.2 and GCC 15 trunk.
---
gdb/testsuite/gdb.cp/m-static.exp | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gdb/testsuite/gdb.cp/m-static.exp b/gdb/testsuite/gdb.cp/m-static.exp
index 19eb70b7d71..45bc090d01f 100644
--- a/gdb/testsuite/gdb.cp/m-static.exp
+++ b/gdb/testsuite/gdb.cp/m-static.exp
@@ -79,14 +79,14 @@ if { [is_aarch32_target] } {
"simple object class, ptype constructor"
gdb_test "print test1.~gnu_obj_1" \
- { = {void \*\(gnu_obj_1 \* const, int\)} 0x[0-9a-f]+ <gnu_obj_1::~gnu_obj_1\(\)>} \
+ { = {void \*\(gnu_obj_1 \* const(, int)?\)} 0x[0-9a-f]+ <gnu_obj_1::~gnu_obj_1\(\)>} \
"simple object instance, print destructor"
gdb_test "ptype test1.~gnu_obj_1" \
- {type = void \*\(gnu_obj_1 \* const, int\)} \
+ {type = void \*\(gnu_obj_1 \* const(, int)?\)} \
"simple object instance, ptype destructor"
gdb_test "print test1.'~gnu_obj_1'" \
- { = {void \*\(gnu_obj_1 \*( const)?, int\)} 0x[0-9a-f]+ <gnu_obj_1::~gnu_obj_1\(\)>} \
+ { = {void \*\(gnu_obj_1 \*( const)?(, int)?\)} 0x[0-9a-f]+ <gnu_obj_1::~gnu_obj_1\(\)>} \
"simple object instance, print quoted destructor"
gdb_test "ptype gnu_obj_1::'~gnu_obj_1'" \
base-commit: e14f6ec969d788b73ac61f61e8c623536cda1cad
--
2.44.0
next reply other threads:[~2024-05-10 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 20:33 Jason Merrill [this message]
2024-05-11 21:56 ` Kevin Buettner
2024-05-14 14:40 ` Tom Tromey
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=20240510203409.1897598-1-jason@redhat.com \
--to=jason@redhat.com \
--cc=gdb-patches@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).