delorie.com/archives/browse.cgi | search |
From: | "Charles Sandmann" <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Compiling Quake |
Date: | Wed, 15 Aug 2001 20:48:11 |
Organization: | Aspen Technology, Inc. |
Lines: | 13 |
Message-ID: | <3b7ae00b.sandmann@clio.rice.edu> |
References: | <3B7AC29A DOT 9080305 AT edu DOT stadia DOT fi> |
NNTP-Posting-Host: | dcloan.hou.aspentech.com |
X-Trace: | selma.aspentech.com 997926791 23764 10.32.115.107 (16 Aug 2001 01:53:11 GMT) |
X-Complaints-To: | postmaster AT aspentech DOT com |
NNTP-Posting-Date: | 16 Aug 2001 01:53:11 GMT |
X-NewsEditor: | ED-1.5.8 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
> I just tried and it compiles with GCC 3.0. You WILL get crashes when you > run it, anybody want to explain that ugly memory management stuff? I haven't looked at the source but I helped them build it. What do you want to know about the memory management? The release was built with DJGPP V2.0 beta 3 pre-release, which only had unixy sbrk() at the time (which is now not the default). To make the unixy sbrk() be non-moving extra memory was allocated (to DPMI commit it) and then a negative sbrk() sent to leave extra for various libc usages. Then there was the locking stuff to get around W95 DPMI lies and strangeness on DMA buffers.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |