From: Kevin Buettner <kevinb@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>, Kevin Buettner <kevinb@cygnus.com>
Cc: Mark Kettenis <kettenis@wins.uva.nl>, gdb@sources.redhat.com
Subject: Re: [RFC] ptid_get_pid function vs. PIDGET macro
Date: Wed, 10 Oct 2001 00:01:00 -0000 [thread overview]
Message-ID: <1011010070055.ZM12213@ocotillo.lan> (raw)
In-Reply-To: <3BC3DC5D.4070609@cygnus.com>
On Oct 10, 1:27am, Andrew Cagney wrote:
> > Anyway, the reason I'd prefer to do things in this order is that
> > ptid_get_lwp() is used for fetching both LWP ids and thread ids
> > on Unixware. If we get carried away and replace all of the macros
> > with their functional equivalents, it may be a lot harder to sort
> > things out for the SCO port at some point in the future.
>
> The unixware thread code has a number of potential cleanups (some of
> which would involve core changes). Since I don't think this will happen
> soon, I think Mark's suggestion should be persued regardless.
>
> Can, instead, the unixware code be localized to unixware files? If that
> is done I can ARI the macro's so that they don't infect new code.
I think it's already fairly localized. There are some places in
generic code which call PIDGET and TIDGET, but now that I think about
it some more, it'd probably be okay to convert / deprecate these. The
files that should NOT be converted are config/i386/tm-i386v42mp.h and
uw-thread.c. So long as we avoid touching these two files (until such
time that these are properly fixed), I withdraw my objection to Mark's
proposal that we deprecate PIDGET, TIDGET, and MERGEPID in the rest of
the sources.
Mark, did you want to do this? Or should I whip up a perl script?
Kevin
next prev parent reply other threads:[~2001-10-10 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 5:58 Mark Kettenis
2001-10-08 15:54 ` Kevin Buettner
2001-10-09 22:28 ` Andrew Cagney
2001-10-10 0:01 ` Kevin Buettner [this message]
2001-10-10 14:02 ` Mark Kettenis
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=1011010070055.ZM12213@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@wins.uva.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