From: "Joachim Schmitz" <jojo@schmitz-digital.de>
To: "'Jan Engelhardt'" <jengelh@inai.de>
Cc: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Subject: RE: [RFC] Support for HP NonStop
Date: Wed, 19 Sep 2012 10:16:15 +0200 [thread overview]
Message-ID: <000001cd963f$0a8421b0$1f8c6510$@schmitz-digital.de> (raw)
In-Reply-To: <alpine.LNX.2.01.1209190923020.32503@nerf07.vanv.qr>
> From: Jan Engelhardt [mailto:jengelh@inai.de]
> Sent: Wednesday, September 19, 2012 9:24 AM
> To: Joachim Schmitz
> Cc: 'Junio C Hamano'; git@vger.kernel.org
> Subject: RE: [RFC] Support for HP NonStop
>
>
> On Friday 2012-08-24 22:43, Joachim Schmitz wrote:
> >
> >> By the way, is "int" wide enough [for intptr_t/uintptr_t],
> >> or should they be "long"?
> >
> >int and long have the same size, 32-bit, here on NonStop.
> >But we do have 64-bit types too. Not sure which to take though.
>
> intptr_t is supposed to hold a void * pointer, so should be
> at least as big.
OK, thanks. We are on IA64 but still use the ILP32 model (so 32bit pointers. Support for LP64 has been added recently, but isn't the
default.
However, long changes from 32bit to 64 bit when changing from ILP32 to LP64, so is the save bet here, right?
prev parent reply other threads:[~2012-09-19 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 19:22 [RFC] Support for HP NonStop Joachim Schmitz
2012-08-24 20:12 ` Junio C Hamano
2012-08-24 20:43 ` Joachim Schmitz
2012-08-24 21:50 ` Junio C Hamano
2012-08-25 8:03 ` Joachim Schmitz
2012-09-19 7:24 ` Jan Engelhardt
2012-09-19 8:16 ` Joachim Schmitz [this message]
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='000001cd963f$0a8421b0$1f8c6510$@schmitz-digital.de' \
--to=jojo@schmitz-digital.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jengelh@inai.de \
/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 NNTP newsgroup(s).