From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/8] Remove object-like target macros
Date: Mon, 28 Sep 2020 19:38:13 -0600 [thread overview]
Message-ID: <87v9fxl5ve.fsf@tromey.com> (raw)
In-Reply-To: <20200721014914.29937-1-tom@tromey.com> (Tom Tromey's message of "Mon, 20 Jul 2020 19:49:06 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> target.h has a number of object-like macros that expand to function
Tom> calls, for example
Tom> #define target_has_memory target_has_memory_1 ()
Tom> This has long seemed confusing to me. This series replaces these
Tom> macros either with function-like macros, or with ordinary function
Tom> calls.
I'm checking this in. I updated a couple of patches to introduce a new
inline function, but seeing as this is a pretty trivial change, I won't
re-send it.
Tom
prev parent reply other threads:[~2020-09-29 1:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 1:49 Tom Tromey
2020-07-21 1:49 ` [PATCH 1/8] Remove target_has_all_memory Tom Tromey
2020-07-21 1:49 ` [PATCH 2/8] Remove target_has_memory macro Tom Tromey
2020-07-21 1:49 ` [PATCH 3/8] Remove target_has_stack macro Tom Tromey
2020-07-21 17:12 ` Christian Biesinger
2020-09-29 1:36 ` Tom Tromey
2020-07-21 1:49 ` [PATCH 4/8] Remove target_has_registers macro Tom Tromey
2020-07-21 1:49 ` [PATCH 5/8] Turn target_can_execute_reverse into function-like macro Tom Tromey
2020-07-21 2:30 ` Simon Marchi
2020-07-21 17:07 ` Christian Biesinger
2020-09-29 1:36 ` Tom Tromey
2020-07-21 1:49 ` [PATCH 6/8] Remove target_has_execution macro Tom Tromey
2020-07-21 1:49 ` [PATCH 7/8] Turn target_can_lock_scheduler into a function-like macro Tom Tromey
2020-07-21 2:32 ` Simon Marchi
2020-07-21 11:28 ` Tom Tromey
2020-09-29 1:37 ` Tom Tromey
2020-07-21 1:49 ` [PATCH 8/8] Turn target_have_steppable_watchpoint into " Tom Tromey
2020-09-29 1:38 ` Tom Tromey [this message]
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=87v9fxl5ve.fsf@tromey.com \
--to=tom@tromey.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).