From: Lancelot SIX <lsix@lancelotsix.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 3/3] gdb/amdgpu: add precise-memory support
Date: Fri, 15 Sep 2023 18:16:11 +0100 [thread overview]
Message-ID: <20230915171601.cpwzr7yxsfqykdlt@octopus> (raw)
In-Reply-To: <cc953eb3-5c24-4b82-847f-d6fca64dac22@efficios.com>
> > Moving the initialization in the ctor's body would solve the issue
> >
> > explicit amd_dbgapi_inferior_info (inferior *inf,
> > bool precise_memory_requested = false)
> > : inf {inf}
> > {
> > precise_memory.requested = precise_memory_requested;
> > }
> >
> > The alternative would be to name
> > amd_dbgapi_inferior_info::precise_memory's type and give it a ctor.
>
> In this case I would just do:
>
> diff --git a/gdb/amd-dbgapi-target.c b/gdb/amd-dbgapi-target.c
> index 507824decf8d..40baf156d83f 100644
> --- a/gdb/amd-dbgapi-target.c
> +++ b/gdb/amd-dbgapi-target.c
> @@ -119,8 +119,10 @@ struct amd_dbgapi_inferior_info
> {
> explicit amd_dbgapi_inferior_info (inferior *inf,
> bool precise_memory_requested = false)
> - : inf {inf}, precise_memory {precise_memory_requested}
> - {}
> + : inf (inf)
> + {
> + precise_memory.requested = precise_memory_requested;
> + }
That would work for me.
Lancelot.
>
> /* Backlink to inferior. */
> inferior *inf;
>
> ---
>
> Or, we can just have two separate fields (precise_memory_requested and
> precise_memory_enabled), they don't really need to be in a struct.
>
> Simon
next prev parent reply other threads:[~2023-09-15 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 14:52 [PATCH v3 1/3] gdb: add inferior_cloned observable Simon Marchi
2023-09-15 14:52 ` [PATCH v3 2/3] gdb/testsuite: add linux target check in allow_hipcc_tests Simon Marchi
2023-09-15 17:19 ` Lancelot SIX
2023-09-15 20:18 ` Simon Marchi
2023-09-15 14:52 ` [PATCH v3 3/3] gdb/amdgpu: add precise-memory support Simon Marchi
2023-09-15 16:04 ` Lancelot SIX
2023-09-15 16:29 ` Simon Marchi
2023-09-15 17:16 ` Lancelot SIX [this message]
2023-09-15 20:19 ` 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=20230915171601.cpwzr7yxsfqykdlt@octopus \
--to=lsix@lancelotsix.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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).