From: Daniel Jacobowitz <drow@false.org>
To: Steve Ellcey <sje@cup.hp.com>
Cc: gdb-patches@gcc.gnu.org
Subject: Re: Patch for gdb build on hppa hp-ux
Date: Tue, 10 Apr 2007 12:05:00 -0000 [thread overview]
Message-ID: <20070410120547.GB18255@caradoc.them.org> (raw)
In-Reply-To: <200704092325.QAA13441@hpsje.cup.hp.com>
On Mon, Apr 09, 2007 at 04:25:38PM -0700, Steve Ellcey wrote:
> Looks good. After I added a local change to use -Wno-char-subscripts
> when building gdb (patch to be submitted) I was able to build with your
> patch. I also ran the gdb testsuite and it went from 432 unexpected
> errors down to 357 after adding your patch. Most of the new passes are
> in the gdb.cp section.
That's peculiar, but I'll accept it. It must come from not calling
pxdb or trying to parse system libraries for debug information, since
the hpacc-abi.c code apparently has not been enabled in years; I went
trying to figure out how it was turned on today and lo and behold, it
never is.
I checked in the patch. Steve, Eli, does this NEWS addition look
reasonable? I believe it's accurate for what I've removed, but I am
not a user of HP-UX or aCC, so I'm guessing a little bit.
--
Daniel Jacobowitz
CodeSourcery
2007-04-10 Daniel Jacobowitz <dan@codesourcery.com>
* NEWS: Mention removal of HP aCC support.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.220
diff -u -p -r1.220 NEWS
--- NEWS 31 Mar 2007 10:42:22 -0000 1.220
+++ NEWS 10 Apr 2007 12:04:27 -0000
@@ -127,6 +127,13 @@ DWARF 1 support
A debug information format. The predecessor to DWARF 2 and
DWARF 3, which are still supported.
+Support for the HP aCC compiler on HP-UX/PA-RISC
+
+ SOM-encapsulated symbolic debugging information, automatic
+ invocation of pxdb, and the aCC custom C++ ABI. This does not
+ affect HP-UX for Itanic or GCC for HP-UX/PA-RISC. Code compiled
+ with aCC can still be debugged on an assembly level.
+
*** Changes in GDB 6.6
* New targets
next prev parent reply other threads:[~2007-04-10 12:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 21:53 Steve Ellcey
2007-04-07 17:20 ` Daniel Jacobowitz
2007-04-09 2:13 ` Daniel Jacobowitz
2007-04-09 23:25 ` Steve Ellcey
2007-04-10 12:05 ` Daniel Jacobowitz [this message]
2007-04-10 12:11 ` Daniel Jacobowitz
2007-04-10 17:32 ` Steve Ellcey
2007-04-10 17:41 ` Daniel Jacobowitz
2007-04-10 19:03 ` Eli Zaretskii
2007-04-10 20:22 ` Daniel Jacobowitz
2007-04-13 14:04 ` Daniel Jacobowitz
2007-04-13 17:07 ` [patch] "single step" atomic instruction sequences as a whole on PPC Luis Machado
2007-04-28 23:34 ` [RFC] " Luis Machado
2007-04-28 23:45 ` Ulrich Weigand
2007-04-29 1:53 ` Luis Machado
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=20070410120547.GB18255@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@gcc.gnu.org \
--cc=sje@cup.hp.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