public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Kai Tietz <Kai.Tietz@onevision.com>
To: iant@google.com
Cc: binutils@sourceware.org, gcc-patches@gcc.gnu.org,
	        gdb-patches@sourceware.org
Subject: Re: patch: libiberty pex for _WIN64
Date: Mon, 06 Aug 2007 07:07:00 -0000	[thread overview]
Message-ID: <OF24CF10F5.24AAFC19-ONC125732F.0026D5F2-C125732F.0027218D@onevision.de> (raw)
In-Reply-To: <20070804163550.GA29463@ednor.casa.cgf.cx>

Hi Christopher,

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

The _WIN64 headers are released under the Snapshot mingw-w64-headers (as 
the new crt for this platform). The pid_t is defined there in sys/types.h.
I think that the headers may get merged with the 32-bit version, but I am 
not quite certain about that. Therefore I try to open an repository on 
sourceforge for them and let them run in parallel.

Cheers,
 i.A. Kai Tietz

|  (\_/)  This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.

------------------------------------------------------------------------------------------
  OneVision Software Entwicklungs GmbH & Co. KG
  Dr.-Leo-Ritter-Straße 9 - 93049 Regensburg
  Tel: +49.(0)941.78004.0 - Fax: +49.(0)941.78004.489 - www.OneVision.com
  Commerzbank Regensburg - BLZ 750 400 62 - Konto 6011050
  Handelsregister: HRA 6744, Amtsgericht Regensburg
  Komplementärin: OneVision Software Entwicklungs Verwaltungs GmbH
  Dr.-Leo-Ritter-Straße 9 – 93049 Regensburg
  Handelsregister: HRB 8932, Amtsgericht Regensburg - Geschäftsführer: 
Ulrike Döhler, Manuela Kluger


  reply	other threads:[~2007-08-06  7:07 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
2007-08-06  7:07       ` Kai Tietz [this message]
     [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=OF24CF10F5.24AAFC19-ONC125732F.0026D5F2-C125732F.0027218D@onevision.de \
    --to=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).