Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@www.cgsoftware.com>
To: Stan Shebs <shebs@apple.com>
Cc: Per Bothner <per@bothner.com>, <gdb-patches@sources.redhat.com>
Subject: Re: obvious set_cu_language patch
Date: Fri, 08 Jun 2001 14:34:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0106081733340.22762-100000@www.cgsoftware.com> (raw)
In-Reply-To: <3B213D7A.AB6568C@apple.com>

On Fri, 8 Jun 2001, Stan Shebs wrote:

> Per Bothner wrote:
> >
> > Daniel Berlin <dan@cgsoftware.com> writes:
> >
> > > dwarf2.h in gcc defines DW_LANG_Java as 0x000b.
> > > binutils/gdb's include/elf/dwarf2.h defines DW_LANG_Java as 0x9af4
> >
> > > Which is correct?
> >
> > I was going to say that I didn't know.  But then I found:
> >         http://reality.sgi.com/dehnert_engr/dwarf/d2-summary.html
> > Draft 6, page 139, lists:
> >         DW_LANG_Java 0x000b
> >
> > I'll fix include/elf/dwarf2.h.  I'm sure Stu Groassman just picked a
> > random number unlikely to conflict with some other assignment.
>
> When Stu did this, there was no mention of Java in the still-drafty
> Dwarf 2 spec.  What's in GCC includes Dwarf 2.1 draft, so it's more
> recent, but beware of many inconsistencies.  (diff of gcc/dwarf2.h
> and include/elf/dwarf2.h is positively scary, since they're supposed
> to be identical)
>
> Will GDB need to be able to recognize the old language code, perhaps
> in an old piece of gcj output?

Depends on how you look at it.
We couldn't before, obviously, and nobody complained, so ...
>  You could  leave the old code in
> dwarf2.h, just give it a different symbolic name.
>

> Stan
>


  reply	other threads:[~2001-06-08 14:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07 23:22 Per Bothner
2001-06-07 23:50 ` Daniel Berlin
2001-06-08 11:01   ` Per Bothner
2001-06-08 14:04     ` Stan Shebs
2001-06-08 14:34       ` Daniel Berlin [this message]
2001-06-08 13:04 ` Andrew Cagney
     [not found]   ` <m2pucevgf6.fsf@kelso.bothner.com>
2001-06-08 13:51     ` Daniel Berlin
     [not found]       ` <8766e6eke4.fsf@creche.redhat.com>
2001-06-08 14:23         ` Per Bothner
     [not found]       ` <npelsq28sh.fsf_-_@zwingli.cygnus.com>
2001-06-11 11:43         ` Rewriting the type system Daniel Berlin
2001-06-11 16:58           ` Stan Shebs
2001-06-12  1:44           ` Eli Zaretskii
2001-06-12  9:12             ` Daniel Berlin
2001-06-12 10:01               ` Eli Zaretskii
2001-06-12 10:16           ` Jim Blandy
2001-06-12 10:44             ` Daniel Berlin
2001-06-12 14:02               ` Stan Shebs
2001-06-13  1:45                 ` Eli Zaretskii
2001-06-12 11:08             ` Daniel Berlin
2001-06-12 14:03           ` Andrew Cagney
2001-06-12 21:37             ` Daniel Berlin
2001-06-25 14:13 ` obvious set_cu_language patch Elena Zannoni

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=Pine.LNX.4.33.0106081733340.22762-100000@www.cgsoftware.com \
    --to=dan@www.cgsoftware.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=per@bothner.com \
    --cc=shebs@apple.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