From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-ID: <u9u2w9j4jr.fsf@yorick.cygnus.com>
References: <19990221144644.M8783.cygnus.egcs@rjlhome.sco.com> <199902230124.RAA24440.cygnus.egcs@rtl.cygnus.com> <u9yalmi70w.fsf@yorick.cygnus.com> <19990225143649.I17655@rjlhome.sco.com>
X-SW-Source: 1999-02n/msg01301.html
Message-ID: <19990228225300.LCBDAXGFPM5wFbRHgrgBvCfbNFLALcIbG2yAD6FQ_PI@z>

>>>>> 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