Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFC] process/thread/lwp id patch - phase 1
Date: Thu, 03 May 2001 01:24:00 -0000	[thread overview]
Message-ID: <1010503082356.ZM4975@ocotillo.lan> (raw)
In-Reply-To: <Pine.SUN.3.91.1010503102025.26629B-100000@is>

On May 3, 10:20am, Eli Zaretskii wrote:

> > 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.

It wasn't in the patch I posted.  It already exists in defs.h.

> > 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.

Yes.  If one of those four (target specific) header files doesn't
define MERGEPID, then it'll get defined by the (already existing)
define in defs.h.

Kevin


  reply	other threads:[~2001-05-03  1:24 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
2001-05-03  1:24       ` Kevin Buettner [this message]
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=1010503082356.ZM4975@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@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