Message-ID: <20020724052031.65847.qmail@web11305.mail.yahoo.com>
Date: Tue, 23 Jul 2002 22:20:31 -0700 (PDT)
From: Pedro Izecksohn <izecksohn AT yahoo DOT com>
Subject: ILP32 - Fwd: Re: 16 bit buffer
To: ohei AT snafu DOT de
Cc: djgpp AT delorie DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Reply-To: djgpp AT delorie DOT com

   More acronyms to your list.
   ILP32 is really a nice one.

--- Bart Oldeman <bart DOT oldeman AT bristol DOT ac DOT uk> wrote:
> From Bart Oldeman Tue Jul 23 13:53:10 2002
> From: Bart Oldeman <bart DOT oldeman AT bristol DOT ac DOT uk>
> Subject: Re: 16 bit buffer
> Date: Tue, 23 Jul 2002 20:53:10 GMT
> To: djgpp AT delorie DOT com
> 
> On Tue, 23 Jul 2002, Richard Dawe wrote:
> 
> > Martin Str|mberg wrote:
> > >
> > > Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk> wrote:
> > > : I believe DJGPP has the ILP32 convention - integers, longs
> and pointers
> > > : are 32
> > >
> > > Is that acronym a standard one. (I don't think I've heard it
> defore.)
> >
> > Yes, but I haven't seen it used that often. See ILP32 and LP64
> mentioned here:
> >
> >
>
http://www.hgmp.mrc.ac.uk/cgi-bin/man.cgi?section=5&topic=standards
> 
> And there are more references to be found using google.
> 
> a few common ones
> I16L32P16 or IP16 ("small/tiny" model)
> I16LP32 or LP32 ("large" model)
> ILP32 ("flat" model, DJGPP, Win32, most common now)
> I32LP64 or LP64 (64-bit *nix)
> IL32P64 or LLP64 or P64 (Win64)
> 
> The last one is a little funny since a pointer does not fit in a
> long any more, i.e.,
> char *b = &foo; unsigned long a = (unsigned long)b; truncates.
> and size_t is a "long long" or "__int64".
> 
> Bart
> 


__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com