public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@cygnus.com>
To: Robert Lipe <robertl@sco.com>
Cc: wilson@cygnus.com, egcs@cygnus.com
Subject: Re: dwarf2 debug dependent upon GAS?
Date: Thu, 25 Feb 1999 18:13:00 -0000	[thread overview]
Message-ID: <u9u2w9j4jr.fsf@yorick.cygnus.com> (raw)
In-Reply-To: Robert Lipe's message of Thu, 25 Feb 1999 14:36:49 -0600

>>>>> Robert Lipe <robertl@sco.com> writes:

 > Our staff that was around at the time of the original SVR4 on 3B2
 > (remember, SCO bought The Organization Formerly Known As USL) says their
 > assembler/linker didn't do this.

OK.

 > What would be the best way to handle this?  Something like letting
 > ASM_OUTPUT_SECTION_NAME watch for the first time any of the 'debug_'
 > sections are emitted and then letting it emit a symbol of the same name?

Nah, just spit out the useful ones in dwarf2out_init.

 > The random symbol could be the section name, right?

I'd suggest a variant on the section name so we can use that solution for
all targets.

Jason

WARNING: multiple messages have this Message-ID
From: Jason Merrill <jason@cygnus.com>
To: Robert Lipe <robertl@sco.com>
Cc: wilson@cygnus.com, egcs@cygnus.com
Subject: Re: dwarf2 debug dependent upon GAS?
Date: Sun, 28 Feb 1999 22:53:00 -0000	[thread overview]
Message-ID: <u9u2w9j4jr.fsf@yorick.cygnus.com> (raw)
Message-ID: <19990228225300.LCBDAXGFPM5wFbRHgrgBvCfbNFLALcIbG2yAD6FQ_PI@z> (raw)
In-Reply-To: <19990225143649.I17655@rjlhome.sco.com>

>>>>> Robert Lipe <robertl@sco.com> writes:

 > Our staff that was around at the time of the original SVR4 on 3B2
 > (remember, SCO bought The Organization Formerly Known As USL) says their
 > assembler/linker didn't do this.

OK.

 > What would be the best way to handle this?  Something like letting
 > ASM_OUTPUT_SECTION_NAME watch for the first time any of the 'debug_'
 > sections are emitted and then letting it emit a symbol of the same name?

Nah, just spit out the useful ones in dwarf2out_init.

 > The random symbol could be the section name, right?

I'd suggest a variant on the section name so we can use that solution for
all targets.

Jason

  parent reply	other threads:[~1999-02-25 18:13 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19990221144644.M8783.cygnus.egcs@rjlhome.sco.com>
1999-02-22 17:24 ` Jim Wilson
     [not found]   ` < 199902230124.RAA24440@rtl.cygnus.com >
1999-02-22 21:32     ` Robert Lipe
     [not found]       ` < 19990222233200.P325@rjlhome.sco.com >
1999-02-23  7:04         ` Brian Ford
     [not found]           ` < Pine.SGI.4.03.9902230903340.512-100000@uscream.vss.fsi.com >
1999-02-23  8:41             ` Robert Lipe
     [not found]               ` < 19990223104109.E2294@rjlhome.sco.com >
1999-02-23  9:03                 ` Brian Ford
1999-02-28 22:53                   ` Brian Ford
1999-02-23 17:39               ` Daniel Berlin
1999-02-28 22:53                 ` Daniel Berlin
1999-02-28 22:53               ` Robert Lipe
1999-02-28 22:53           ` Brian Ford
1999-02-23 14:19         ` Jim Wilson
1999-02-28 22:53           ` Jim Wilson
1999-02-28 22:53       ` Robert Lipe
1999-02-28 22:53   ` Jim Wilson
     [not found] ` <199902230124.RAA24440.cygnus.egcs@rtl.cygnus.com>
1999-02-25 12:05   ` Jason Merrill
     [not found]     ` <19990225143649.I17655@rjlhome.sco.com>
1999-02-25 18:13       ` Jason Merrill [this message]
     [not found]         ` < u9u2w9j4jr.fsf@yorick.cygnus.com >
1999-02-25 20:55           ` Robert Lipe
1999-02-25 21:02             ` Jason Merrill
     [not found]               ` < u9d82xiwp5.fsf@yorick.cygnus.com >
1999-02-25 21:21                 ` Robert Lipe
1999-02-25 21:27                   ` Jason Merrill
1999-02-28 22:53                     ` Jason Merrill
1999-02-28 22:53                   ` Robert Lipe
1999-02-25 22:16                 ` Robert Lipe
1999-02-25 22:31                   ` Jason Merrill
     [not found]                     ` < u93e3tism2.fsf@yorick.cygnus.com >
1999-02-25 23:25                       ` Robert Lipe
     [not found]                         ` < 19990226012522.D17655@rjlhome.sco.com >
1999-02-28  0:57                           ` Jeffrey A Law
1999-02-28 22:53                             ` Jeffrey A Law
1999-02-28 22:53                         ` Robert Lipe
1999-02-28 22:53                     ` Jason Merrill
1999-02-28 22:53                   ` Robert Lipe
1999-02-28 22:53               ` Jason Merrill
1999-02-25 21:19             ` Jason Merrill
1999-02-28 22:53               ` Jason Merrill
1999-02-28 22:53             ` Robert Lipe
1999-02-28 22:53         ` Jason Merrill
1999-02-28 22:53     ` Jason Merrill
1999-02-21 12:47 Robert Lipe
     [not found] ` < 19990221144644.M8783@rjlhome.sco.com >
1999-02-21 14:51   ` Jeffrey A Law
1999-02-28 22:53     ` Jeffrey A Law
1999-02-28 22:53 ` Robert Lipe

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=u9u2w9j4jr.fsf@yorick.cygnus.com \
    --to=jason@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=robertl@sco.com \
    --cc=wilson@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).