From: Bruno Larsen <blarsen@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v5 0/7] Clean gdb.base when testing with clang
Date: Wed, 14 Sep 2022 15:14:20 +0200 [thread overview]
Message-ID: <20220914131427.269689-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 v5:
* Removed patches previously numbered 1,4-11 given Andrew's approval
* Split previous patch 3 in two, to make it more focused
* Reworded some commits
* Dropped patch 13, in favor of Andrew's suggestion (not included).
Changes in v4:
* Added new test to step through a function's epoligue
* renamed gdb_step_until_regexp -> gdb_step_until
* small style and wording changes in patches 1 and 2
* Dropped patch 3 - no longer necessary
* patch 4 was reworked based on Andrew's suggestion
small note, Andrew has OK'd patched 5 and 6 (currently 4 and 5) in v3;
Changes in v3:
* Fixed some issues that only showed up on CXX_FOR_TARGET=clang
* rebased on current master
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 (7):
gdb/testsuite: Add a proc to test where compiler links the epilogue
Change gdb.base/skip-solib.exp deal with lack of epilogue information
gdb/testsuite: fix testing gdb.base/skip-inline.exp with clang
gdb/testsuite: fix gdb.base/msym-bp-shl when running with Clang
fix gdb.base/jit-elf.exp when testing with clang
gdb.base/skip.exp: Use finish to exit functions
gdb/testsuite: Add test to step through function epilogue
gdb/testsuite/gdb.base/jit-elf.exp | 2 +-
gdb/testsuite/gdb.base/msym-bp-shl-main-2.c | 2 +-
gdb/testsuite/gdb.base/skip-inline.exp | 107 ++++++++++--------
gdb/testsuite/gdb.base/skip-solib-lib.c | 3 +-
gdb/testsuite/gdb.base/skip-solib-main.c | 3 +-
gdb/testsuite/gdb.base/skip.exp | 34 +++---
.../gdb.base/step-through-epilogue.c | 38 +++++++
.../gdb.base/step-through-epilogue.exp | 98 ++++++++++++++++
gdb/testsuite/lib/gdb.exp | 32 ++++++
9 files changed, 253 insertions(+), 66 deletions(-)
create mode 100644 gdb/testsuite/gdb.base/step-through-epilogue.c
create mode 100644 gdb/testsuite/gdb.base/step-through-epilogue.exp
--
2.37.3
next reply other threads:[~2022-09-14 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 13:14 Bruno Larsen [this message]
2022-09-14 13:14 ` [PATCH v5 1/7] gdb/testsuite: Add a proc to test where compiler links the epilogue Bruno Larsen
2022-09-14 13:14 ` [PATCH v5 2/7] Change gdb.base/skip-solib.exp deal with lack of epilogue information Bruno Larsen
2022-09-14 13:14 ` [PATCH v5 3/7] gdb/testsuite: fix testing gdb.base/skip-inline.exp with clang Bruno Larsen
2022-09-14 13:14 ` [PATCH v5 4/7] gdb/testsuite: fix gdb.base/msym-bp-shl when running with Clang Bruno Larsen
2022-09-14 13:14 ` [PATCH v5 5/7] fix gdb.base/jit-elf.exp when testing with clang Bruno Larsen
2022-09-14 13:14 ` [PATCH v5 6/7] gdb.base/skip.exp: Use finish to exit functions Bruno Larsen
2022-09-14 13:14 ` [PATCH v5 7/7] gdb/testsuite: Add test to step through function epilogue Bruno Larsen
2022-09-21 16:05 ` [PATCH v5 0/7] Clean gdb.base when testing with clang Tom Tromey
2022-09-22 9:05 ` 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=20220914131427.269689-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).