From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: iant@google.com, gdb-patches@sourceware.org,
binutils@sourceware.org, Kai.Tietz@onevision.com,
gcc-patches@gcc.gnu.org
Subject: Re: patch: libiberty pex for _WIN64
Date: Sat, 04 Aug 2007 16:35:00 -0000 [thread overview]
Message-ID: <20070804163550.GA29463@ednor.casa.cgf.cx> (raw)
In-Reply-To: <uabt7bsfg.fsf@gnu.org>
On Sat, Aug 04, 2007 at 11:44:03AM +0300, Eli Zaretskii wrote:
>> Date: Fri, 3 Aug 2007 19:16:42 -0400
>> From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
>>
>> >2007-08-03 Kai Tietz <kai.tietz@onevision.com>
>> >
>> > * pex-common.h: (pex_funcs): Retyped wait and exec_child to pid_t.
>> > * pex-djgpp.c: Likewise.
>> > * pex-msdos.c: Likewise.
>> > * pex-unix.c: Likewise.
>> > * pex-win32.c: Likewise.
>>
>> If long isn't long enough what is pid_t defined to be on _WIN64?
>
>I think it's "long long", as 64-bit Windows uses the P64 model.
Yeah, duh. That was obvious. Sorry.
Where does the "typedef long long pid_t" come from? I only see it as
being defined as "int" in the mingw headers. And I didn't see any
machinery in configure to derive this.
I guess I'm asking if there is another patch coming down the line which
handles the long long.
cgf
next prev parent reply other threads:[~2007-08-04 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 15:32 Kai Tietz
2007-08-03 16:03 ` Ian Lance Taylor
2007-08-07 14:18 ` Kai Tietz
2007-08-03 23:16 ` Christopher Faylor
2007-08-04 8:44 ` Eli Zaretskii
2007-08-04 16:35 ` Christopher Faylor [this message]
2007-08-06 7:07 ` Kai Tietz
[not found] <m3y7gwkoz0.fsf@localhost.localdomain>
2007-08-03 15:01 ` 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=20070804163550.GA29463@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=Kai.Tietz@onevision.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=iant@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).