From: Bruno Larsen <blarsen@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 00/11] gdb/testsuite: Cleanup gdb.base for clang testing
Date: Mon, 11 Apr 2022 17:13:22 -0300 [thread overview]
Message-ID: <20220411201333.81453-1-blarsen@redhat.com> (raw)
When testing GDB with clang, gdb.base had over 50 more failures than when
testing with gcc. Examining the failed tests led to a few clang bugs, a
few GDB bugs, and many testsuite assumptions that could be changed.
After this patch series, nothing should be changed for testing with gcc,
and testing with clang should only show non-trivial failures for
maint.exp and macscp.exp, along with the same GCC failures.
Changes in v2:
* Introduced gdb_step_until_regexp, based on Pedro's and Andrew's suggestions
* reworked fixes for: skip.exp, skip-solib.exp and msym-bp-shl.exp
* Used Pedro's suggestion for call-ar-st
* reordered patches slightly
Bruno Larsen (11):
gdb/testsuite: introduce gdb_step_until_regexp
Change gdb.base/skip-solib.exp deal with lack of epilogue information
change gdb.base/skip.exp to use finish instead of step
change gdb.base/symbol-alias to xfail with clang
change gdb.base/nodebug.c to not fail with clang
update gdb.base/info-program.exp to not fail with clang
fix gdb.base/access-mem-running.exp for clang testing
Fix gdb.base/call-ar-st to work with Clang
add xfails to gdb.base/complex-parts.exp when testing with clang
gdb/testsuite: fix gdb.base/msym-bp-shl when running with Clang
explicitly test for stderr in gdb.base/dprintf.exp
gdb/testsuite/gdb.base/access-mem-running.c | 2 +-
gdb/testsuite/gdb.base/call-ar-st.exp | 13 +-
gdb/testsuite/gdb.base/complex-parts.exp | 5 +
gdb/testsuite/gdb.base/dprintf.exp | 10 ++
gdb/testsuite/gdb.base/info-program.exp | 2 +-
gdb/testsuite/gdb.base/msym-bp-shl.exp | 8 +
gdb/testsuite/gdb.base/nodebug.c | 2 +-
gdb/testsuite/gdb.base/nodebug.exp | 2 +-
gdb/testsuite/gdb.base/skip-inline.exp | 18 ++-
gdb/testsuite/gdb.base/skip-solib-lib.c | 3 +-
gdb/testsuite/gdb.base/skip-solib-main.c | 3 +-
gdb/testsuite/gdb.base/skip-solib.exp | 12 +-
gdb/testsuite/gdb.base/skip.exp | 164 ++++++++++++++++----
gdb/testsuite/gdb.base/symbol-alias.exp | 9 +-
gdb/testsuite/lib/gdb.exp | 30 ++++
15 files changed, 232 insertions(+), 51 deletions(-)
--
2.31.1
next reply other threads:[~2022-04-11 20:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 20:13 Bruno Larsen [this message]
2022-04-11 20:13 ` [PATCH v2 01/11] gdb/testsuite: introduce gdb_step_until_regexp Bruno Larsen
2022-04-11 20:13 ` [PATCH v2 02/11] Change gdb.base/skip-solib.exp deal with lack of epilogue information Bruno Larsen
2022-04-11 20:13 ` [PATCH v2 03/11] change gdb.base/skip.exp to use finish instead of step Bruno Larsen
2022-04-12 18:11 ` Bruno Larsen
2022-05-17 16:38 ` Bruno Larsen
2022-04-11 20:13 ` [PATCH v2 04/11] change gdb.base/symbol-alias to xfail with clang Bruno Larsen
2022-04-11 20:13 ` [PATCH v2 05/11] change gdb.base/nodebug.c to not fail " Bruno Larsen
2022-04-11 20:13 ` [PATCH v2 06/11] update gdb.base/info-program.exp " Bruno Larsen
2022-04-11 20:13 ` [PATCH v2 07/11] fix gdb.base/access-mem-running.exp for clang testing Bruno Larsen
2022-04-11 20:13 ` [PATCH v2 08/11] Fix gdb.base/call-ar-st to work with Clang Bruno Larsen
2022-04-11 20:13 ` [PATCH v2 09/11] add xfails to gdb.base/complex-parts.exp when testing with clang Bruno Larsen
2022-04-11 20:13 ` [PATCH v2 10/11] gdb/testsuite: fix gdb.base/msym-bp-shl when running with Clang Bruno Larsen
2022-04-11 20:13 ` [PATCH v2 11/11] explicitly test for stderr in gdb.base/dprintf.exp Bruno Larsen
2022-04-26 13:17 ` [PING] [PATCH v2 00/11] gdb/testsuite: Cleanup gdb.base for clang testing Bruno Larsen
2022-05-03 20:43 ` [PINGv2] " Bruno Larsen
2022-05-10 20:06 ` [PINGv3] " 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=20220411201333.81453-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).