From: Duncan Sands <duncan.sands@math.u-psud.fr>
To: Joel Brobecker <brobecker@gnat.com>
Cc: Hilfinger@otisco.mckusick.com, gdb@sources.redhat.com
Subject: Re: Meaning of "Builds libada directory"
Date: Wed, 13 Oct 2004 20:26:00 -0000 [thread overview]
Message-ID: <200410131659.25122.duncan.sands@math.u-psud.fr> (raw)
In-Reply-To: <20041007142823.GF1282@gnat.com>
On Thursday 07 October 2004 16:28, Joel Brobecker wrote:
> > > Hmm. Haven't seen this, but then I don't use that compiler. I
> > > shall inquire. Just out of curiosity, if you stop somewhere in Ada
> > > source, what language do you see?
> >
> > minimal:
>
> I think I know why. I am a bit in a rush this morning, so I'll
> let you try the attached patch, see if it makes a difference.
> The key here is that 3.15p uses stabs, while recent GCC versions
> use dwarf2, where the language is set from the DW_LANG value,
> rather than the source extension.
>
> 2004-10-07 Joel Brobecker <brobecker@gnat.com>
>
> * dwarf2read.c (set_cu_language): Set language to Ada for
> DW_LANG_Ada83 and DW_LANG_Ada95.
>
> It is almost obvious, but I want to test it before I submit this
> patch and I can't do it this morning. Do give it a try.
Hi Joel, I see that this patch didn't go in yet. Was there something
wrong with it? It seems to work fine here.
All the best,
Duncan.
next prev parent reply other threads:[~2004-10-13 14:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410061940.i96JeCLF003487@tully.CS.Berkeley.EDU>
2004-10-07 6:28 ` Paul N. Hilfinger
2004-10-07 6:32 ` Duncan Sands
2004-10-07 6:42 ` Duncan Sands
2004-10-07 6:49 ` Paul N. Hilfinger
2004-10-07 6:50 ` Duncan Sands
2004-10-07 14:48 ` Joel Brobecker
2004-10-07 14:55 ` Duncan Sands
2004-10-13 20:26 ` Duncan Sands [this message]
2004-10-13 20:33 ` Joel Brobecker
2004-10-07 7:08 ` Duncan Sands
2004-10-06 18:58 Duncan Sands
2004-10-06 19:02 ` Daniel Jacobowitz
2004-10-06 21:26 ` Duncan Sands
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=200410131659.25122.duncan.sands@math.u-psud.fr \
--to=duncan.sands@math.u-psud.fr \
--cc=Hilfinger@otisco.mckusick.com \
--cc=brobecker@gnat.com \
--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