Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: Is anyone using the HP compilers on PA-RISC with FSF GDB?
Date: Fri, 04 Aug 2006 12:50:00 -0000	[thread overview]
Message-ID: <20060804125031.GA26799@nevyn.them.org> (raw)
In-Reply-To: <20060804050024.GB60709@mail1.thewrittenword.com>

On Fri, Aug 04, 2006 at 12:00:24AM -0500, Albert Chin wrote:
> On Tue, Aug 01, 2006 at 10:55:30PM -0400, Daniel Jacobowitz 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
> > 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++?
> 
> We use them to build most of the free software we provide for our
> customers.
> 
> > I have not heard from any users of the FSF GDB with the HP compilers in
> > a long time; for HP-specific features, I suspect more people use HP's
> > WDB fork of GDB.  If no one is using the HP support, I would like to
> > remove it from the next release of GDB.
> 
> We ship GDB for all platforms except HP-UX, where we ship HP's WDB.

May I make sure I follow this correctly - on HP-UX, you use the aCC
compilers, but do not use GDB?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-08-04 12:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-01 15:12 RFC: getting rid of deprecated_hp_som_som_object_present Randolph Chung
2006-03-02  5:57 ` Jim Blandy
2006-08-02  2:55 ` Is anyone using the HP compilers on PA-RISC with FSF GDB? Daniel Jacobowitz
2006-08-04  5:00   ` Albert Chin
2006-08-04 12:50     ` Daniel Jacobowitz [this message]
2006-08-11 15:54       ` Albert Chin

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=20060804125031.GA26799@nevyn.them.org \
    --to=drow@false.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