Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!blake!djo7613
From: djo7613@blake.acs.washington.edu (Dick O'Connor)
Newsgroups: comp.sys.ibm.pc
Subject: Turbo C 1.5 malloc bug??
Keywords: malloc, Turbo C 1.5, memory models
Message-ID: <362@blake.acs.washington.edu>
Date: 7 Dec 88 16:32:51 GMT
Organization: Univ of Washington, Seattle
Lines: 14

In article 1346, the poster related a Turbo C 1.5 bug involving malloc.
Now I know nothing about assembler worth noting, but our local expert
gave the posting a scan and contributed the following, for what it may
be worth:

Compilation under large or huge memory models optimizing for speed generates
32-bit pointers, and only 386/68030 machines with 32-bit pointer capability
on the bus can run such code.  Suggestions include using a 386 machine, 
compiling under a different memory model if possible, optimizing for size
instead of speed, and not optimizing at all.
   
-Dick O'Connor, Washington Department of Fisheries

Disclaimer: It's my word against his!