From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/6] The DWARF assembler and Clang
Date: Fri, 11 Nov 2022 16:36:19 +0000 [thread overview]
Message-ID: <cover.1668184173.git.aburgess@redhat.com> (raw)
In a reply to a recent mailing list message of mine, it was mentioned
that the DWARF assembler doesn't work with Clang.
I know that once upon a time this was the case, but I thought those
problems had long been fixed, but I did some investigation anyway.
I ran all the tests that mention 'Dwarf::assemble' and compared the
results between gcc and Clang. This series addresses all the
regressions that I found.
The general summary is that the DWARF assembler works fine with Clang.
All the issues I found were minor, and specific to individual tests.
The final patch converts an existing test to use the DWARF assembler,
when I proposed this earlier the feedback was the DWARF assembler
doesn't work with Clang. My claim is that it's fine, and switching to
the DWARF assembler will increase test coverage.
Thanks,
Andrew
---
Andrew Burgess (6):
gdb/testsuite: don't avoid DWARF assembler tests with Clang
gdb/testsuite: fix gdb.trace/unavailable-dwarf-piece.exp with Clang
gdb/testsuite: fix gdb.compile/compile-ops.exp with clang
gdb/testsuite: add (and use) a new build-id compile option
gdb/testsuite: fix gdb.debuginfod/fetch_src_and_symbols.exp with Clang
gdb/testsuite: rewrite gdb.cp/call-method-register.exp with dwarf
assembler
.../gdb.base/until-trailing-insns.exp | 6 -
gdb/testsuite/gdb.compile/compile-ops.c | 8 +-
gdb/testsuite/gdb.compile/compile-ops.exp | 18 ++-
gdb/testsuite/gdb.cp/call-method-register.cc | 49 +-------
gdb/testsuite/gdb.cp/call-method-register.exp | 108 +++++++++++++-----
.../gdb.cp/incomplete-type-overload.exp | 5 -
.../gdb.debuginfod/fetch_src_and_symbols.exp | 25 +++-
.../gdb.trace/unavailable-dwarf-piece.exp | 4 +-
gdb/testsuite/lib/gdb.exp | 9 ++
9 files changed, 130 insertions(+), 102 deletions(-)
base-commit: db2e277d1a840091f56185d94f9d39c6736d2556
--
2.25.4
next reply other threads:[~2022-11-11 16:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 16:36 Andrew Burgess [this message]
2022-11-11 16:36 ` [PATCH 1/6] gdb/testsuite: don't avoid DWARF assembler tests with Clang Andrew Burgess
2022-11-11 16:36 ` [PATCH 2/6] gdb/testsuite: fix gdb.trace/unavailable-dwarf-piece.exp " Andrew Burgess
2022-11-16 14:41 ` Bruno Larsen
2022-11-17 11:06 ` Andrew Burgess
2022-12-12 17:55 ` Tom Tromey
2022-12-13 15:39 ` Andrew Burgess
2022-11-11 16:36 ` [PATCH 3/6] gdb/testsuite: fix gdb.compile/compile-ops.exp with clang Andrew Burgess
2022-11-16 16:27 ` Tom Tromey
2022-11-11 16:36 ` [PATCH 4/6] gdb/testsuite: add (and use) a new build-id compile option Andrew Burgess
2022-11-11 16:36 ` [PATCH 5/6] gdb/testsuite: fix gdb.debuginfod/fetch_src_and_symbols.exp with Clang Andrew Burgess
2022-11-16 16:29 ` Tom Tromey
2022-11-17 11:38 ` [PATCHv2 0/2] Fix " Andrew Burgess
2022-11-17 11:38 ` [PATCHv2 1/2] gdb/testsuite: rename source file gdb.debuginfod/main.c Andrew Burgess
2022-11-17 11:38 ` [PATCHv2 2/2] gdb/testsuite: fix gdb.debuginfod/fetch_src_and_symbols.exp with Clang Andrew Burgess
2022-11-17 19:29 ` [PATCHv2 0/2] Fix " Tom Tromey
2022-11-11 16:36 ` [PATCH 6/6] gdb/testsuite: rewrite gdb.cp/call-method-register.exp with dwarf assembler Andrew Burgess
2022-11-16 11:59 ` Lancelot SIX
2022-11-16 16:32 ` [PATCH 0/6] The DWARF assembler and Clang Tom Tromey
2022-11-18 11:48 ` Andrew Burgess
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=cover.1668184173.git.aburgess@redhat.com \
--to=aburgess@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).