From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stan Shebs <shebs@apple.com>
To: Per Bothner <per@bothner.com>
Cc: Daniel Berlin <dan@cgsoftware.com>, gdb-patches@sources.redhat.com
Subject: Re: obvious set_cu_language patch
Date: Fri, 08 Jun 2001 14:04:00 -0000
Message-id: <3B213D7A.AB6568C@apple.com>
References: <m24rtrwkfd.fsf@kelso.bothner.com> <874rtrjwis.fsf@cgsoftware.com> <m2u21qvo3y.fsf@kelso.bothner.com>
X-SW-Source: 2001-06/msg00177.html

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?  You could leave the old code in
dwarf2.h, just give it a different symbolic name.

Stan