All of lore.kernel.org
 help / color / mirror / Atom feed
From: n0ano@indstorage.com
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] C union on ia-64
Date: Thu, 25 Oct 2001 14:36:06 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805394@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805377@msgid-missing>

Yeah, I know that NT uses a P64 model but if you'll look at
the caption of the slide in question it is for `Linux Device
Drivers'.  Anyone who typedef's `ULONG' to anything other than 
a 64-bit long on IA64 Linux deserves the confusion that that
will create.

Actually, I believe I was at John's presentation of this slide
set and I'm pretty sure he clarified all of this during his
talk.  This just points out the danger of looking at just a
set of slides.  Without the author to explain things it can
be easy to misinterpret things.

On Thu, Oct 25, 2001 at 09:12:51AM +0800, Tang, Yu wrote:
> /* size.c */
> #include "stido.h"
> int main(int argc, char *argv[])
> {
> 	printf("%d,%d\n",sizeof(unsigned long),sizeof(void*));
> 	return 0;
> }
> 
> under linux:
> $gcc size.c -o size
> $./size
> 8,8
> 
> under 64-bit WinXP:
> c:\temp\size
> 4,8
> 
> -----Original Message-----
> From: KOCHI, Takayoshi [mailto:t-kouchi@mvf.biglobe.ne.jp]
> Sent: 2001å¹´10æoe^25æ-¥ 3:50
> To: linux-64
> Subject: Re: [Linux-ia64] C union on ia-64
> 
> 
> > PS: Interestingly enought, I believe Intel's slide is actually
> > wrong.  If `ULONG' is an `unsigned long' and `PVOID' is a `void *'
> > then all of the data items have the same size and the two structures
> > can be used interchangably on either IA32 or IA64.  It's a
> > dangerous technique but it would work in this case.
> 
> I believe win64 uses P64 for its programming model.
> (while we use LP64 instead)
> So their ULONG is still 32bit in IA64.
> 
> Regards,
> -- 
> KOCHI Takayoshi <t-kouchi@cq.jp.nec.com/t-kouchi@mvf.biglobe.ne.jp>
> 
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@indstorage.com
Ph: 303/652-0870x117


  parent reply	other threads:[~2001-10-25 14:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-23 19:03 [Linux-ia64] C union on ia-64 Gururaj Ananthateerta
2001-10-24 11:35 ` Andreas Schwab
2001-10-24 18:52 ` Gururaj Ananthateerta
2001-10-24 19:46 ` Andreas Schwab
2001-10-24 19:46 ` Boehm, Hans
2001-10-24 19:50 ` n0ano
2001-10-24 19:50 ` KOCHI, Takayoshi
2001-10-25  1:12 ` Tang, Yu
2001-10-25 14:36 ` n0ano [this message]
2001-10-31 23:16 ` Jes Sorensen

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=marc-linux-ia64-105590698805394@msgid-missing \
    --to=n0ano@indstorage.com \
    --cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.