public inbox for
 help / color / mirror / Atom feed
From: Jason Merrill <>
To: Robert Lipe <>
Subject: Re: patch was: dwarf2 debug dependent upon GAS?
Date: Thu, 11 Mar 1999 00:02:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

>>>>> Robert Lipe <> writes:

[ context: SCO as doesn't support referring to the section name as a
symbol, so we're changing the dwarf2 code in gcc to spit out a label to use
instead. ]

 >>  >> shortening the label names, so as to use less space in the symbol
 >>  >> table.
 >>  > They're locals, so they don't go in the symbol table, right?
 >>  > They certainly don't appear in nm or even a 'strings -a' of the
 >>  > resulting dot-o.
 >> Don't they?  I thought they would, since we are creating relocs
 >> against them.

 > Uuuh, no.  That's how we started this discussion.  The section name
 > was treated as a local label for the beginning of the section in this
 > compilation unit.   Therefore, they're completely local and don't need
 > to appear in the symbol table.

This is irrelevant to your patch, but on Linux the local symbols do show up
in the symbol table, as I remembered; I always filter nm output as a
result.  This may be a gas thing.  Any gas folk care to comment?


       reply	other threads:[~1999-03-11  0:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <>
     [not found]       ` <>
     [not found]         ` <>
     [not found]           ` <>
1999-03-11  0:02             ` Jason Merrill [this message]
1999-03-11  7:41               ` Ian Lance Taylor
1999-03-11 10:31                 ` Jason Merrill
1999-03-11 10:44                   ` Ian Lance Taylor
1999-03-11 11:20                     ` Jason Merrill
1999-03-11 18:02                       ` Ian Lance Taylor

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).