From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Use enum for call_dummy_location
Date: Tue, 18 Oct 2022 10:15:31 -0600 [thread overview]
Message-ID: <20221018161533.3089756-1-tromey@adacore.com> (raw)
I wanted to change the gdbarch call_dummy_location to use an enum,
instead of a couple of #defines. This required a bit of work in
gdbarch.py, and this series is the result.
Tom
next reply other threads:[~2022-10-18 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 16:15 Tom Tromey [this message]
2022-10-18 16:15 ` [PATCH 1/2] Inline initialization of gdbarch members Tom Tromey
2022-10-26 9:33 ` Bruno Larsen
2022-10-31 15:03 ` Tom Tromey
2022-10-18 16:15 ` [PATCH 2/2] Use enum for gdbarch's call_dummy_location Tom Tromey
2022-10-26 11:57 ` Bruno Larsen
2022-10-26 11:25 ` [PATCH 0/2] Use enum for call_dummy_location Luis Machado
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=20221018161533.3089756-1-tromey@adacore.com \
--to=tromey@adacore.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).