From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add initializers to bound_minimal_symbol
Date: Fri, 11 Feb 2022 08:34:06 -0500 [thread overview]
Message-ID: <d0e8a06a-bc13-e1a0-1bbb-1baea2a0fb4f@polymtl.ca> (raw)
In-Reply-To: <20220208204245.2186900-1-tromey@adacore.com>
On 2022-02-08 15:42, Tom Tromey via Gdb-patches wrote:
> This adds initializers to bound_minimal_symbol, allowing for the
> removal of some calls to memset.
I was trying to see if it would be better to have a constructor (with
two arguments instead), so that we would never have an uninitialized
bound_minimal_symbol. But there are cases where we really want to
initialize it as "empty" and then check for emptiness later, so your
change makes sense.
Simon
next prev parent reply other threads:[~2022-02-11 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 20:42 Tom Tromey
2022-02-11 13:34 ` Simon Marchi [this message]
2022-02-14 15:53 ` Simon Marchi
2022-02-15 15:41 ` Tom Tromey
2022-02-16 14:31 ` Enze Li
2022-02-16 15:29 ` Simon Marchi
2022-02-16 20:47 ` Tom Tromey
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=d0e8a06a-bc13-e1a0-1bbb-1baea2a0fb4f@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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).