From: Jeffrey A Law <law@hurl.cygnus.com>
To: Robert Lipe <robertlipe@usa.net>
Cc: egcs@egcs.cygnus.com
Subject: Re: dwarf2 debug dependent upon GAS?
Date: Sun, 28 Feb 1999 22:53:00 -0000 [thread overview]
Message-ID: <7675.919637363@hurl.cygnus.com> (raw)
Message-ID: <19990228225300.7GA-4A5cDDZ1nc5_N7k1XQQl4gO92t5m5tvOAAD8Mcg@z> (raw)
In-Reply-To: <19990221144644.M8783@rjlhome.sco.com>
In message < 19990221144644.M8783@rjlhome.sco.com >you write:
> I've had it on my list to examine Dwarf2 debugging for System V. I'm
> finding that it seems to depend upon a curiosity of the GNU assembler.
> Is this accurate?
>
> I'm seeing EGCS (current trunk) generate refences to symbols that don't
> exist. There are SECTIONS of that name, but no symbols. Apparently
> GAS treat them interchangably. Is it the intent for these to reference
> the beginning of the section in this file (i.e. local labels) or the
> beginning of that section once linked? (without making them global, I
> don't know how I would synthesize that.)
This sounds vaguely familiar. I think this has been hashed before on the
egcs lists. Attempts to change this behavior caused some other set of
assemblers to blow chunks, or relocation problems or something else goofy.
We probably need some way to fine tune this particular behavior.
jeff
next prev parent reply other threads:[~1999-02-28 22:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-21 12:47 Robert Lipe
[not found] ` < 19990221144644.M8783@rjlhome.sco.com >
1999-02-21 14:51 ` Jeffrey A Law [this message]
1999-02-28 22:53 ` Jeffrey A Law
1999-02-28 22:53 ` Robert Lipe
[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
[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
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=7675.919637363@hurl.cygnus.com \
--to=law@hurl.cygnus.com \
--cc=egcs@egcs.cygnus.com \
--cc=robertlipe@usa.net \
/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).