From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
carlos@baldric.uwo.ca, dave.anglin@nrc-cnrc.gc.ca,
gdb@sources.redhat.com
Subject: Re: gdb 6.0
Date: Mon, 01 Mar 2004 20:16:00 -0000 [thread overview]
Message-ID: <20040301201603.GA11102@nevyn.them.org> (raw)
In-Reply-To: <40439982.8010407@gnu.org>
On Mon, Mar 01, 2004 at 03:13:54PM -0500, Andrew Cagney wrote:
> >>Yes, and HP/UX support in the current CVS source is pretty good;
>
> I wouldn't go that far (I can get away with saying that 'cos its been me
> hacking on it :-). The 32-bit PA support is, lets say, "functional".
>
> >> but
> >> the PA Linux patches will not apply without some serious work.
>
> >I have some cleanups for HP/UX which I can now submit as my gdb
> >paperwork is now complete. I did a build last night and a few new
> >warnings have appeared since early Jan.
> >
> >Carlos had offered to work on getting the debian PA Linux patches
> >integrated.
>
> Can I suggest worrying about -nat changes? As Daniel hints, anything to
> hppa-tdep.c is probably no longer applicable (or needs serious thought).
These patches didn't use hppa-tdep.c at all - they created a parallel
pa-tdep.c without HP/UX support. Beyond that I have absolutely zero
idea what the differences are.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2004-03-01 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 18:11 John David Anglin
2004-03-01 18:14 ` Daniel Jacobowitz
2004-03-01 18:33 ` John David Anglin
2004-03-01 18:36 ` Daniel Jacobowitz
2004-03-01 18:42 ` John David Anglin
2004-03-01 20:14 ` Andrew Cagney
2004-03-01 20:16 ` Daniel Jacobowitz [this message]
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=20040301201603.GA11102@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=carlos@baldric.uwo.ca \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--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