From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: FYI: minor simplification in add_psymbol_to_bcache
Date: Thu, 05 Nov 2009 22:16:00 -0000 [thread overview]
Message-ID: <m38wekty66.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20091105200252.GA18502@caradoc.them.org> (Daniel Jacobowitz's message of "Thu, 5 Nov 2009 15:02:52 -0500")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
>> On Wed, Nov 04, 2009 at 12:16:27PM -0700, Tom Tromey wrote:
>> TBH I was not thinking too soundly, I suppose, when I nuked this. I
>> think your point is a good one. If you'd prefer, I will leave this
>> static and just zero out that field.
Daniel> Unless you have a good reason not to, I suggest making that change.
Here is the patch I am checking in.
Tom
2009-11-05 Tom Tromey <tromey@redhat.com>
* symfile.c (add_psymbol_to_bcache): Make 'psymbol' static again.
Zero the 'value' field.
Index: symfile.c
===================================================================
RCS file: /cvs/src/src/gdb/symfile.c,v
retrieving revision 1.253
diff -u -r1.253 symfile.c
--- symfile.c 5 Nov 2009 19:53:04 -0000 1.253
+++ symfile.c 5 Nov 2009 22:15:30 -0000
@@ -3105,9 +3105,15 @@
enum language language, struct objfile *objfile,
int *added)
{
- struct partial_symbol psymbol;
-
- memset (&psymbol, 0, sizeof (struct partial_symbol));
+ /* psymbol is static so that there will be no uninitialized gaps in the
+ structure which might contain random data, causing cache misses in
+ bcache. */
+ static struct partial_symbol psymbol;
+
+ /* However, we must ensure that the entire 'value' field has been
+ zeroed before assigning to it, because an assignment may not
+ write the entire field. */
+ memset (&psymbol.ginfo.value, 0, sizeof (psymbol.ginfo.value));
/* val and coreaddr are mutually exclusive, one of them *will* be zero */
if (val != 0)
{
prev parent reply other threads:[~2009-11-05 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 20:10 Tom Tromey
2009-11-03 20:21 ` Daniel Jacobowitz
2009-11-04 19:16 ` Tom Tromey
2009-11-05 20:03 ` Daniel Jacobowitz
2009-11-05 22:16 ` 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=m38wekty66.fsf@fleche.redhat.com \
--to=tromey@redhat.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