From: Bruno Larsen <blarsen@redhat.com>
To: gdb-patches@sourceware.org
Cc: Bruno Larsen <blarsen@redhat.com>
Subject: [PATCH v2 0/9] Cleanup gdb.cp tests when running with clang
Date: Mon, 7 Nov 2022 14:45:56 +0100 [thread overview]
Message-ID: <20221107134604.596986-1-blarsen@redhat.com> (raw)
Following my previous series, where I tried to reduce the amount of
failures when running gdb.base tests using clang, I moved to reducing
errors in gdb.cp.
Actual GDB issues are being addressed in separate patches, and this
series is confined to just changing tests to either work or
XFAIL/disable them, to make it simpler to keep track of issues.
Changelog for v2:
* Pushed 2 patches that were approved by Andrew
* Added language test for all test_compiler calls
* Added some logic to new compilation flags
* Addressed all patch-specific comments from Andrew
Bruno Larsen (9):
gdb/testsuite: ignore Non-C-typedefs for gdb.cp/class2.exp
gdb/testsuite: enable running gdb.cp/classes.exp with clang
gdb/testsuite: account for clang's nested destructor calls on
gdb.cp/mb-ctor.exp
gdb/testsuite: add XFAIL to gdb.cp/derivation.exp when using Clang
gdb/testsuite: allow for Clang style destructors on
gdb.cp/m-static.exp
gdb/testsuite: skip gdb.cp/anon-struct.exp when using Clang
gdb/testsuite: disable some tests of gdb.cp/typeid.exp when using
Clang
gdb/testsuite: remove XFAIL on gdb.cp/temargs.exp
gdb/testsuite: disable gdb.cp/call-method-register.exp when not using
gcc
gdb/testsuite/gdb.cp/anon-struct.exp | 10 ++++++
gdb/testsuite/gdb.cp/call-method-register.exp | 5 +++
gdb/testsuite/gdb.cp/class2.exp | 9 ++++-
gdb/testsuite/gdb.cp/classes.exp | 36 ++++++++++++++++++-
gdb/testsuite/gdb.cp/derivation.exp | 4 +++
gdb/testsuite/gdb.cp/m-static.exp | 11 +++---
gdb/testsuite/gdb.cp/mb-ctor.exp | 18 ++++++++++
gdb/testsuite/gdb.cp/temargs.exp | 6 ++--
gdb/testsuite/gdb.cp/typeid.exp | 10 +++++-
9 files changed, 99 insertions(+), 10 deletions(-)
--
2.37.3
next reply other threads:[~2022-11-07 13:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 13:45 Bruno Larsen [this message]
2022-11-07 13:45 ` [PATCH v2 1/9] gdb/testsuite: ignore Non-C-typedefs for gdb.cp/class2.exp Bruno Larsen
2022-11-07 13:45 ` [PATCH v2 2/9] gdb/testsuite: enable running gdb.cp/classes.exp with clang Bruno Larsen
2022-11-07 13:45 ` [PATCH v2 3/9] gdb/testsuite: account for clang's nested destructor calls on gdb.cp/mb-ctor.exp Bruno Larsen
2022-11-07 13:46 ` [PATCH v2 4/9] gdb/testsuite: add XFAIL to gdb.cp/derivation.exp when using Clang Bruno Larsen
2022-11-07 13:46 ` [PATCH v2 5/9] gdb/testsuite: allow for Clang style destructors on gdb.cp/m-static.exp Bruno Larsen
2022-11-07 13:46 ` [PATCH v2 6/9] gdb/testsuite: skip gdb.cp/anon-struct.exp when using Clang Bruno Larsen
2022-11-07 13:46 ` [PATCH v2 7/9] gdb/testsuite: disable some tests of gdb.cp/typeid.exp " Bruno Larsen
2022-11-07 13:46 ` [PATCH v2 8/9] gdb/testsuite: remove XFAIL on gdb.cp/temargs.exp Bruno Larsen
2022-11-10 18:21 ` Tom Tromey
2022-11-07 13:46 ` [PATCH v2 9/9] gdb/testsuite: disable gdb.cp/call-method-register.exp when not using gcc Bruno Larsen
2022-11-10 18:24 ` [PATCH v2 0/9] Cleanup gdb.cp tests when running with clang Tom Tromey
2022-11-11 8:38 ` Bruno Larsen
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=20221107134604.596986-1-blarsen@redhat.com \
--to=blarsen@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).