From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH 0/2] Fix some trivial build failures with clang
Date: Mon, 25 Mar 2024 14:27:58 -0400 [thread overview]
Message-ID: <20240325183011.1037710-1-simon.marchi@efficios.com> (raw)
Fix two trivial build failures when building with Clang. I see more
problems, but they were not as trivial, so I'm leaving them for another
patch series.
Simon Marchi (2):
gdb: mark addrmap classes `final`
gdbserver/Makefile.in: add missing `-x c++`
gdb/addrmap.h | 6 +++---
gdbserver/Makefile.in | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
base-commit: 7879fba359f185d674d4e981af4f23a066bfe644
--
2.44.0
next reply other threads:[~2024-03-25 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 18:27 Simon Marchi [this message]
2024-03-25 18:27 ` [PATCH 1/2] gdb: mark addrmap classes `final` Simon Marchi
2024-03-25 18:28 ` [PATCH 2/2] gdbserver/Makefile.in: add missing `-x c++` Simon Marchi
2024-03-26 0:33 ` [PATCH 0/2] Fix some trivial build failures with clang Tom Tromey
2024-03-26 1:49 ` Simon Marchi
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=20240325183011.1037710-1-simon.marchi@efficios.com \
--to=simon.marchi@efficios.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