Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: dave@hiauly1.hia.nrc.ca
Cc: dave@hiauly1.hia.nrc.ca, gdb-patches@sources.redhat.com,
	randolph@tausq.org
Subject: Re: [patch] Remove uses of deprecated_registers from hppah-nat.c
Date: Sat, 20 Nov 2004 18:36:00 -0000	[thread overview]
Message-ID: <200411201835.iAKIZvQj001652@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <200411201804.iAKI43Kl020796@hiauly1.hia.nrc.ca> (dave@hiauly1.hia.nrc.ca)

   Date: Sat, 20 Nov 2004 13:04:03 -0500 (EST)
   From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>

   > 2004-11-20  John David Anglin  <dave.anglin@nrc-cnrc.gc.ca>
   > 
   > 	* infttrace.h (ttrace_write_reg_64): Add prototype.
   > 	* hppah-nat.c (store_inferior_registers): Fix warning from ambiguous
   > 	expression.  
   > 	(store_inferior_registers): Correct formatting.  Replace uses of
   > 	deprecated_registers with calls to regcache_raw_read,
   > 	regcache_raw_write_part and regcache_raw_read_part.

Please check this in.  It's obviously correct since it removes
deprecated stuff and makes things build again ;-) We can always fix
any fallout later.

   > HP-UX 11(i) is still broken; it really needs a clean new inf-ttrace.c.
   > You might get away with configuring GDB with --host=hppa-hp-hpux10.20
   > on HP-UX 11(i) if you don't care about threads support.

   I've been doing quite a few HP-UX 11(i) build as Randolph added fixes.
   Sure, a lot of stuff is broken but a lot of stuff works as well.  For
   example, watchpoint support surprisingly works on hppa64.

I think I was more talking about 10.20 than 11.x when I said that most
of the fancy stuff was broken anyway.

   > We can discuss changes required to fix the hpux target, but let's not
   > assume that hpux support will be gone in the next release (which is
   > what's currently in the NEWS file...)

   Bah, it appears that I have wasted my time given the politics of HP-UX
   support in the gdb project.

Well, your patch removes the reason why HP-UX was listed to be removed
in the NEWS file.  So a big thank-you from me (and probably all other
people with an interest in HP-UX).

About the politics.  Everything except GNU/Linux is a second class
citizen in GNU-land.  I really hope that given enough support from the
userbase we can give other platforms a place too.  I'll stronly oppose
any unreasonable attempt to remove features that such platforms depend
on.

Unfortunately the HP-UX support in GDB has many problems.  It'll
require a significant amount of work to keep it alive.  I hope you'll
continue to help with that.

Personally, I think we can increase the likelyhood of continued HP-UX
support by getting rid of some of the badly implemented HP-UX-only
features.  That's why I just committed that HP-UX 10.20 change.
Hopefully we can do something like it for HP-UX 11.x.  I sincerely
hope you don't view this as if I'm throwing away the stuff that you
spent hours of time on to get it working again.

Mark


  reply	other threads:[~2004-11-20 18:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <no.id>
2004-11-20 18:04 ` John David Anglin
2004-11-20 18:36   ` Mark Kettenis [this message]
2004-11-21  0:23     ` John David Anglin
2004-11-20 17:45 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=200411201835.iAKIZvQj001652@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=gdb-patches@sources.redhat.com \
    --cc=randolph@tausq.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