Newsgroups:	comp.os.msdos.djgpp
From:	Bart Oldeman <bart DOT oldeman AT bristol DOT ac DOT uk>
Subject:	Re: 16 bit buffer
Sender:	unknown AT pg5 DOT enm DOT bris DOT ac DOT uk (Address not verified)
Organization:	University of Bristol, UK
Message-ID:	<Pine.LNX.4.44.0207232125210.339-100000@pg5.enm.bris.ac.uk>
References:	<3d391151 DOT 2522562 AT news DOT onet DOT pl> <3D392BF0 DOT BC4558B8 AT phekda DOT freeserve DOT co DOT uk>
	<1027424406 DOT 515621 AT queeg DOT ludd DOT luth DOT se> <3D3DA859 DOT 10E69781 AT phekda DOT freeserve DOT co DOT uk>
Mime-Version:	1.0
X-X-Sender:	enbeo AT pg5 DOT enm DOT bris DOT ac DOT uk
In-Reply-To:	<3D3DA859.10E69781@phekda.freeserve.co.uk>
Date:	Tue, 23 Jul 2002 20:53:10 GMT
Lines:	30
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv 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

- Raw text -