From: "Tom Tromey (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Christian Biesinger <cbiesinger@google.com>, gdb-patches@sourceware.org
Subject: [review v2] Add static_asserts for the sizes of space-critical structs
Date: Tue, 29 Oct 2019 19:22:00 -0000 [thread overview]
Message-ID: <20191029192216.9EED220AF6@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1572028967000.Idd68320aa3e79ee7cc749019724636a58ce4b9c6@gnutoolchain-gerrit.osci.io>
Tom Tromey has posted comments on this change.
Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/306
......................................................................
Patch Set 2: Code-Review+1
(1 comment)
I think these spots should maybe come with a short comment explaining
that the assert is just to make sure you don't change the size by
accident. That way people changing the size on purpose will know
they can just update the assert. WDYT?
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/306/2/gdb/symtab.h
File gdb/symtab.h:
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/306/2/gdb/symtab.h@1189
PS2, Line 1189:
1180 | /* FIXME drow/2003-02-21: For the LOC_BLOCK case, it might be better
1181 | to add a magic symbol to the block containing this information,
1182 | or to have a generic debug info annotation slot for symbols. */
1183 |
1184 | void *aux_value;
1185 |
1186 | struct symbol *hash_next;
1187 | };
1188 |
1189 | gdb_static_assert ((sizeof (void *) == 8 && sizeof (symbol) == 72) ||
|| at the start of the next line.
--
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: Idd68320aa3e79ee7cc749019724636a58ce4b9c6
Gerrit-Change-Number: 306
Gerrit-PatchSet: 2
Gerrit-Owner: Christian Biesinger <cbiesinger@google.com>
Gerrit-Reviewer: Tom Tromey <tromey@sourceware.org>
Gerrit-Comment-Date: Tue, 29 Oct 2019 19:22:16 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
next prev parent reply other threads:[~2019-10-29 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 18:42 [review] " Christian Biesinger (Code Review)
2019-10-29 19:22 ` Tom Tromey (Code Review) [this message]
2019-11-04 17:43 ` [review v3] " Christian Biesinger (Code Review)
2019-11-04 17:44 ` [review v4] " Christian Biesinger (Code Review)
2019-11-04 17:56 ` Tom Tromey (Code Review)
2019-11-04 18:14 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-04 18:14 ` Sourceware to Gerrit sync (Code Review)
2019-11-13 9:47 ` Szabolcs Nagy
2019-11-13 20:06 ` Christian Biesinger via gdb-patches
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=20191029192216.9EED220AF6@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=gnutoolchain-gerrit@osci.io \
/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