public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: David Taylor <dtaylor@emc.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: stabs and macro information
Date: Wed, 16 Apr 2003 17:16:00 -0000	[thread overview]
Message-ID: <200304161716.h3GHGLN00754@mailhub.lss.emc.com> (raw)
In-Reply-To: Your message of "Wed, 16 Apr 2003 12:47:17 EDT." <159A1846-702B-11D7-83B7-000393575BCC@dberlin.org>

> Date: Wed, 16 Apr 2003 12:47:17 -0400
> From: Daniel Berlin <dberlin@dberlin.org>
> 
> On Wednesday, April 16, 2003, at 11:58  AM, David Taylor wrote:
> 
> > The GCC side of things took less than a day to implement; I'm hoping
> > to get started on the GDB side soon.
> >
> I didn't see it on the GCC list. Was it submitted?
> I ask because ...

Not yet.  The copyright assignment paperwork for EMC's changes to GCC
hasn't been approved/signed yet by management.  I expect it will be
approved/signed, but it hasn't been yet.

[I feel that it is inappropriate to post changes if they are not
assigned (unless they are small enough to not need an assignment).

However, I do feel it is appropriate to discuss how to do it / what to
name things / etc. as the changes are likely to be assigned.]

Also, since the GDB part isn't done yet, the GCC part isn't
particularly useful as yet.

[NOTE: GDB copyright assignment papers *have* been signed.]

> > One question I have is what stabs types to use -- tentatively I'm 
> > using:
> >
> >     /* GNU extension.  Macro define.  */
> >     __define_stab(N_MAC_DEFINE, 0x36, "MAC_DEFINE")
> 
> >     /* GNU extension.  Macro undefine.  */
> >     __define_stab(N_MAC_UNDEF, 0x3a, "MAC_UNDEF")
> >
> Unless these are really generated by GCC, they aren't GNU extensions, 
> they are EMC extensions.

You are correct that they are currently EMC extensions.  After the
change gets submitted, if it is accepted, then it will be a GNU
extension.

> > as it appears (based on gcc/stab.def, include/aout/stab.def, and
> > gdb/doc/stabs.texinfo) that 0x36 and 0x3a are available.
> >
> > Is anyone aware of any other uses of stab types 0x36 and 0x3a --
> > i.e. is anyone aware of uses that might conflict?
> >
> You might want to look at what Sun's tools do.
> Do they generate STABS anymore, and if so, see if they have extensions 
> that conflict here.

I don't currently have access to Sun's tools.  Also, Sun used to be
(might still be for all I know) rather secretive about their stabs
extensions.  Does Sun document their stabs stuff in a publicly
accessible document?

I don't know if Sun's tools still generate stabs or not.

> > Thanks.
> >
> > David
> >
> > p.s. shouldn't include/aout/stab.def and gcc/stab.def be merged?
> 
> Possibly.
> I would imagine that nobody seriously cares about *extending* STABS 
> anymore, so nobody has had any motivation to do anything about it.
> 
> --Dan

Later,

David

  reply	other threads:[~2003-04-16 17:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-16 15:58 David Taylor
2003-04-16 16:47 ` Daniel Berlin
2003-04-16 17:16   ` David Taylor [this message]
2003-04-16 17:25     ` Daniel Jacobowitz
2003-04-16 17:38     ` Andrew Cagney
2003-04-16 17:27 ` Daniel Jacobowitz
2003-04-16 17:59   ` David Taylor
2003-04-16 20:29   ` Daniel Berlin
2003-04-17 16:39     ` David Taylor
2003-04-17 16:46       ` Daniel Jacobowitz
2003-04-24  3:20 ` Jim Blandy

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=200304161716.h3GHGLN00754@mailhub.lss.emc.com \
    --to=dtaylor@emc.com \
    --cc=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).