Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add stabs entries for coalesced symbols.
Date: Mon, 18 Nov 2002 22:59:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1021119085817.10110I-100000@is> (raw)

Forwarded here, since the original message was sent to the wrong list, 
and so was my response.

---------- Forwarded message ----------
Date: Tue, 19 Nov 2002 08:11:29 +0200 (IST)
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Klee Dienes <klee@apple.com>
Cc: binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: [RFA] Add stabs entries for coalesced symbols.


On Mon, 18 Nov 2002, Klee Dienes wrote:

> I suspect there may be a better place to "Relocatable Symbol Blocks"  
> section of the TeXinfo file, but I wasn't able to find it

I don't see anything wrong with your choice, but then I'm not a stabs 
expert.  If someone thinks that another place is better, please speak up.

Your patch is approved, with the following comments/requests:


  +@node Relocatable Symbol Blocks
  +@section Relocatable Symbol Blocks

Please add a @cindex entry here for "relocatable symbol blocks".

  +On Mac OS X, a @dfn{coalesced symbol} is a true definition of a symbol
  +that may appear one or more times in the compilation units generated
  +by the compiler.

It is generally a good idea to have a @cindex entry for each term you put 
inside a @dfn.  The logic is that if the term is important enough to have 
it stand out in the manual, someone will want to find its description 
quickly; using index-search facilities of Info readers is just the way to 
do that.

Also, are coalesced symbols a MacOS-only feature, or are they supported 
(or can reasonably be expected to be supported in the future) on other 
platforms?  If the former, I think we should tell right at the start of 
this section that the information pertains only to the Mac.

  +The static link editor allows multiple definitions of a coalesced
  +symbol without any warnings or errors. The static link editor outputs
                                        ^^^
Please make sure there are exactly 2 spaces after each period that ends a 
sentence.  This is important for TeX to typeset the printed version in a 
pleasant way.

  +@item 0x2e N_BNSYM
  +Start of a relocatble symbolblock; see @ref{Relocatable Symbol Blocks}.
                         ^^^^^^^^^^^
This should be "symbol block", I think.

Thanks!


             reply	other threads:[~2002-11-19  6:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18 22:59 Eli Zaretskii [this message]
     [not found] <1038196445.11584.ezmlm@sources.redhat.com>
2002-11-24 20:21 ` Jim Ingham
     [not found] <C774777A-FB47-11D6-84AF-00039396EEB8@apple.com>
2002-11-18 16:37 ` Klee Dienes
2002-11-18 22:22   ` Ian Lance Taylor
2002-11-24  2:25     ` Klee Dienes
2002-11-24  6:21       ` Eli Zaretskii
2002-12-08 17:00         ` Klee Dienes
2002-12-08 22:39           ` Eli Zaretskii
2002-12-09 10:22             ` Klee Dienes
2002-12-09 12:37               ` Eli Zaretskii
2002-11-24  9:46       ` Ian Lance Taylor
2002-11-24 14:22       ` Jim Blandy
2002-12-06  8:59       ` Nick Clifton

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=Pine.SUN.3.91.1021119085817.10110I-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.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