From: Eli Zaretskii <eliz@is.elta.co.il>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFC] process/thread/lwp id patch - phase 1
Date: Thu, 03 May 2001 00:19:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010503102025.26629B-100000@is> (raw)
In-Reply-To: <1010501144655.ZM545@ocotillo.lan>
On Tue, 1 May 2001, Kevin Buettner wrote:
> > > +#define pid_to_ptid(PID) ((ptid_t) MERGEPID ((PID),0))
> >
> > This definition is global, for all ports and targets. However,
> > MERGEPID is only defined for some of them, so it looks like the other
> > targets will instantly become broken by this change (since pid_to_ptid
> > is called in much more targets than those which define MERGEPID). So
> > I think some header (target.h?) should have a fallback definition for
> > MERGEPID, something like this:
> >
> > #ifndef MERGEPID
> > #define MERGEPID(PID,DUMMY) (PID)
> > #endif
> >
> > Or did I miss something?
>
> MERGEPID will be defined for all ports and all targets since it is
> defined later on in defs.h...
>
> #ifndef PIDGET
> #define PIDGET(PID) (PID)
> #define TIDGET(PID) 0
> #define MERGEPID(PID, TID) (PID)
> #endif
Hmm, I don't see this snippet in defs.h in the patch you posted.
> Also, MERGEPID is defined along with PIDGET in each each header file
> where PIDGET is defined. These are:
>
> config/nm-linux.h
> config/sparc/tm-sun4sol2.h
> config/i386/tm-i386sol2.h
> config/i386/tm-i386v42mp.h
These I do see, but they are specific to these targets. MERGEPID
seems to be required on all targets.
next prev parent reply other threads:[~2001-05-03 0:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 10:45 Kevin Buettner
2001-05-01 1:48 ` Eli Zaretskii
2001-05-01 7:47 ` Kevin Buettner
2001-05-03 0:19 ` Eli Zaretskii [this message]
2001-05-03 1:24 ` Kevin Buettner
2001-05-03 1:28 ` Eli Zaretskii
2001-05-03 15:57 ` Andrew Cagney
2001-05-03 21:31 ` Kevin Buettner
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=Pine.SUN.3.91.1010503102025.26629B-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@cygnus.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