From: Eli Zaretskii <eliz@gnu.org>
To: dje@google.com (Doug Evans)
Cc: tromey@redhat.com, gdb-patches@sourceware.org, ccoutant@google.com
Subject: Re: [RFA] Add global/static and symbol kind indicator to .gdb_index
Date: Tue, 19 Jun 2012 16:08:00 -0000 [thread overview]
Message-ID: <831ulbe14b.fsf@gnu.org> (raw)
In-Reply-To: <20120619074931.6F0B41E136F@ruffy2.mtv.corp.google.com>
> cc: ccoutant@google.com
> Date: Tue, 19 Jun 2012 00:49:31 -0700 (PDT)
> From: dje@google.com (Doug Evans)
>
> This patch adds a global/static bit and a symbol kind indicator
> to CU values in .gdb_index.
Thanks. I have a few comments about the documentation part:
> +If a symbol has multiple uses within a CU then there is one
> +CU index+attributes value for each different use.
I would lose the "different" part, it's redundant here.
> +@item 0
> +This value is reserved and not to be used.
^^^^^^^^^^^^^^^^^^
"and should not be used"
> +@item 2
> +The symbol is a variable.
> +Enum values are also included.
Not sure what the last sentence means. Value is not a symbol. Do you
mean "the symbol is a name of a variable or of an enum"?
And, if my reading of the code is correct, we should mention constants
here.
> +@item 4
> +The symbol is not covered by the other kinds.
I think this is better:
Any other kind of symbol.
> +@item Bit 31
> +This bit is zero if the value is ``global'' and one if it is ``static''.
Do we really need the quotes here?
next prev parent reply other threads:[~2012-06-19 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 7:49 Doug Evans
2012-06-19 14:01 ` Pedro Alves
2012-06-19 16:08 ` Eli Zaretskii [this message]
2012-06-19 19:41 ` Doug Evans
2012-06-22 19:45 ` Tom Tromey
2012-06-22 21:03 ` Tom Tromey
2012-06-22 21:20 ` Cary Coutant
2012-06-23 19:59 ` Doug Evans
2012-06-25 14:53 ` Tom Tromey
2012-06-25 15:06 ` Tom Tromey
2012-06-23 22:25 ` Doug Evans
2012-06-24 8:09 ` Doug Evans
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=831ulbe14b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ccoutant@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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