From: Daniel Jacobowitz <drow@false.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: gdb@sources.redhat.com
Subject: Re: [Fwd: Is anyone using the HP compilers on PA-RISC with FSF GDB?] (fwd)
Date: Wed, 02 Aug 2006 19:22:00 -0000 [thread overview]
Message-ID: <20060802192156.GA27488@nevyn.them.org> (raw)
In-Reply-To: <200608021916.k72JGwFd002315@hiauly1.hia.nrc.ca>
On Wed, Aug 02, 2006 at 03:16:56PM -0400, John David Anglin wrote:
> > > I have a question, though, which I think I've asked before. GCC on
> > > HP/UX uses stabs, so only requires basic SOM support from GDB. That
> >
> > There have been requests for ELF debug support. The main issue as
> > far as I can see is the lack of named sections and where to put stuff.
Do you mean DWARF-2 here? If so, I completely agree. It seems like
SOM has some named sections - at least we're managing to get objdump to
tell me there's a GDB_STRINGS section - so I don't know what the
problem is.
> > > should be in decent shape still. But the stuff read by hpread.c is
> > > only generated by the HP compilers (cc and aCC).
> > >
> > > - Are these compilers still important for C?
> > > - Are these compilers still important for C++?
> >
> > Oh, I'm sure these compilers are still important to some people.
> > However, I don't see the need to maintain support for the debug
> > format generated by these compilers. There's no debug info in any
> > of the system libraries, so this capability doesn't help development
> > of open source applications under HP-UX.
> >
> > I should also say that access to HP compilers is necessary to
> > maintain this code. Thus, it really can only be done by HP. If
> > they don't maintain it, then it should be removed.
At one point in the past, the Compaq testdrive systems offered aCC. I
don't think they do any more though.
Thanks for the response, Dave - if you don't think we need to hold on
to aCC support, then I doubt anyone else will either. However, there's
no need to rush; I'll wait for at least a few weeks, in case anyone
else has comments, and then come back to this if no one does.
> > On the otherhand, GCC C, C++, Ada and Java are now working quite well
> > on PA-RISC for both Linux and HP-UX. So, I would suggest that we need
> > to focus support in these areas. Of course, I'm a bit biased ;)
I'd be much happier working on support for GCC :-) Especially if that
means DWARF-2 debug information!
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-02 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 19:17 John David Anglin
2006-08-02 19:22 ` Daniel Jacobowitz [this message]
2006-08-02 19:46 ` John David Anglin
2006-08-13 14:59 ` [[RFC] DWARF2 debug support for HP-UX SOM target John David Anglin
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=20060802192156.GA27488@nevyn.them.org \
--to=drow@false.org \
--cc=dave@hiauly1.hia.nrc.ca \
--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