From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb-patches@sources.redhat.com
Subject: Re: RFC: threads PREPARE_TO_PROCEED patch
Date: Mon, 26 May 2003 20:05:00 -0000 [thread overview]
Message-ID: <20030526200516.GA29817@nevyn.them.org> (raw)
In-Reply-To: <3ED270EB.3040700@redhat.com>
On Mon, May 26, 2003 at 03:54:19PM -0400, Andrew Cagney wrote:
> [picking up old thread sitting in my in box, added AndreasS]
>
> Can I suggest:
>
> - moving default_prepare_to_proceed() to infrun.c, make it static,
> rename it to prepare_to_proceed().
> - removing PREPARE_TO_PROCEED from the architecture vector
> - renaming HP's (and Mach) PREPARE_TO_PROCEED to
> DEPRECATED_PREPARE_TO_PROCEED
> - tweaking the PREPARE_TO_PROCEED code to use #ifdef'd
> DEPRECATED_PREPARE_TO_PROCEED if available.
That sounds reasonable to me, and saves me having to go and test my
theories on HP/UX :)
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-05-26 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 23:32 Daniel Jacobowitz
2003-03-14 17:20 ` Mark Kettenis
2003-03-14 18:35 ` Daniel Jacobowitz
2003-03-15 20:39 ` Mark Kettenis
2003-03-15 20:51 ` Daniel Jacobowitz
2003-03-16 21:24 ` Andrew Cagney
2003-05-26 19:57 ` Andrew Cagney
2003-05-26 20:05 ` 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=20030526200516.GA29817@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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