From: Steve Ellcey <sje@cup.hp.com>
To: drow@false.org
Cc: gdb-patches@gcc.gnu.org
Subject: Re: Patch for gdb build on hppa hp-ux
Date: Mon, 09 Apr 2007 23:25:00 -0000 [thread overview]
Message-ID: <200704092325.QAA13441@hpsje.cup.hp.com> (raw)
In-Reply-To: <20070409021338.GA28612@caradoc.them.org>
Daniel Jacobowitz wrote:
> Since you can build on HP/UX, could you test this patch for me? It
> removes support for HP aCC, both the custom C++ ABI (which has fingers
> in a lot of other places too, but this is a start) and the custom
> debug format. It should not affect the testsuite when using gcc with
> SOM.
>
> Thanks in advance!
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.
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2007-04-09 23:25 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 [this message]
2007-04-10 12:05 ` Daniel Jacobowitz
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=200704092325.QAA13441@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=drow@false.org \
--cc=gdb-patches@gcc.gnu.org \
/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