From: Ian Lance Taylor <iant@google.com>
To: Kai Tietz <Kai.Tietz@onevision.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: PING: Re: patch: libiberty adjustments for _WIN64
Date: Wed, 01 Aug 2007 01:45:00 -0000 [thread overview]
Message-ID: <m3y7gwkoz0.fsf@localhost.localdomain> (raw)
In-Reply-To: <OFADFAEB2F.815B2727-ONC1257324.0027B55F-C1257324.0027F1F3@onevision.de>
Kai Tietz <Kai.Tietz@onevision.com> writes:
> Daniel Jacobowitz wrote on 25.07.2007 23:48:07:
>
> > On Wed, Jul 25, 2007 at 04:51:02PM -0400, DJ Delorie wrote:
> > >
> > > > As far as I can see, the type used here is never exposed outside of
> > > > the pex_run interface.
> > >
> > > Hmmm.. maybe I was thinking of some other libiberty interface, then.
> > > Perhaps hash tables?
> >
> > I think that was the splay tree keys.
>
> Yes, the splay tree keys are this issue.
>
> But why can't we use the 'pid_t' type for pex ?
Just because the pex code is intended to be highly portable, and not
every system defines a pid_t type. You can use pid_t if you make sure
that it is defined reasonably.
Ian
next prev parent reply other threads:[~2007-08-01 1:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 13:11 Kai Tietz
2007-07-25 15:57 ` Ian Lance Taylor
2007-07-25 20:39 ` DJ Delorie
2007-07-25 20:53 ` Ian Lance Taylor
2007-07-25 21:25 ` DJ Delorie
2007-07-25 21:54 ` Daniel Jacobowitz
2007-07-26 7:51 ` Kai Tietz
2007-08-01 1:45 ` Ian Lance Taylor [this message]
2007-08-03 13:09 ` Kai Tietz
2007-08-03 15:07 ` Ian Lance Taylor
2007-08-03 15:21 ` Kai Tietz
2007-08-03 15:30 ` Ian Lance Taylor
2007-08-03 15:41 ` Kai Tietz
2007-08-03 16:01 ` Ian Lance Taylor
2007-08-03 16:10 ` Kai Tietz
2007-08-03 15:01 ` patch: libiberty pex " Kai Tietz
[not found] <OF00E7FD99.36C5E0BD-ONC1257310.0042A207-C1257310.00442A1C@LocalDomain>
2007-07-16 9:00 ` PING: Re: patch: libiberty adjustments " Kai Tietz
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=m3y7gwkoz0.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=Kai.Tietz@onevision.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).