delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/03/26/12:36:28

From: "Christopher Nelson" <paradox AT gye DOT satnet DOT net>
To: <djgpp AT delorie DOT com>
Subject: Re: memory models
Date: Fri, 26 Mar 1999 06:42:38 -0700
Message-ID: <01be778e$836d6ac0$LocalHost@thendren>
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3
Reply-To: djgpp AT delorie DOT com

-----Original Message-----
From: mario trujilllo <tvazquez AT tamps1 DOT telmex DOT net DOT mx>
To: djgpp AT delorie DOT com <djgpp AT delorie DOT com>
Date: Thursday, March 25, 1999 8:02 AM
Subject: memory models


>PAX.
>      What about memory models and DJGPP??
>      Do you know where can i found info about memory models??
>


Because DJGPP runs in 32-bit flat memory space under the DPMI host, (which
in most cases is hosting a 48-bit segmented "protected" memory model) it
doesn't really run under ANY memory model.

It has access to about 4 gigs worth of memory. If the host (DPMI) can
actually provide this amount of memory, then you can use it.

If you're talking pointers, all pointers are NEAR 32-bit pointers.  You can
use far pointers via the farpointer functions included with DJGPP, but
they're not really far-pointers in the original Microsoft/Borland C
far-pointer system because the compiler doesn't recognize them as "far"
pointers.  As I understand it this is a Unix heritage, which is both good
and bad.

            -={C}=-


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019