From: Simon Marchi <simon.marchi@efficios.com>
To: Tom Tromey <tom@tromey.com>,
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/4] gdb: add type::is_declared_class / type::set_is_declared_class
Date: Thu, 1 Apr 2021 21:14:30 -0400 [thread overview]
Message-ID: <0a9762fb-c1f7-03fc-f55f-0b94a93c9076@efficios.com> (raw)
In-Reply-To: <87lfa1op8g.fsf@tromey.com>
On 2021-04-01 2:04 p.m., Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Simon> Add the `is_declared_class` and `set_is_declared_class` methods on
> Simon> `struct type`, in order to remove the `TYPE_DECLARED_CLASS` macro. In
> Simon> this patch, the macro is changed to use the getter, so all the call
> Simon> sites of the macro that are used as a setter are changed to use the
> Simon> setter method directly. The next patch will remove the macro
> Simon> completely.
>
> Simon> gdb/ChangeLog:
>
> Simon> * gdbtypes.h (struct type) <is_declared_class,
> set_is_declared_class> : New methods.
> Simon> (TYPE_DECLARED_CLASS): Use type::is_declared_class, change all
> Simon> write call sites to use type::set_is_declared_class.
>
> I skimmed through this series and all four of these look reasonable to me.
> Thank you.
>
> Tom
>
Thanks, pushed.
Simon
prev parent reply other threads:[~2021-04-02 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 14:01 Simon Marchi
2021-03-24 14:01 ` [PATCH 2/4] gdb: remove TYPE_DECLARED_CLASS Simon Marchi
2021-03-24 14:01 ` [PATCH 3/4] gdb: add type::is_flag_enum / type::set_is_flag_enum Simon Marchi
2021-03-24 14:01 ` [PATCH 4/4] gdb: remove TYPE_FLAG_ENUM Simon Marchi
2021-04-01 18:04 ` [PATCH 1/4] gdb: add type::is_declared_class / type::set_is_declared_class Tom Tromey
2021-04-02 1:14 ` Simon Marchi [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=0a9762fb-c1f7-03fc-f55f-0b94a93c9076@efficios.com \
--to=simon.marchi@efficios.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).