Path: chuka.playstation.co.uk!scea!greg_labrec@interactive.sony.com From: David White Newsgroups: scea.yaroze.programming.codewarrior Subject: Re: Initializing the heap Date: Tue, 04 Nov 1997 13:07:58 -0800 Organization: SCEA News Server Lines: 13 Message-ID: <345F8EAE.167E@san.rr.com> References: <01bce566$fdb8c1a0$a5bf43ce@wkwerner> <34596659.40D5@charlie.cns.iit.edu> <01bce5de$a390af80$6fbf43ce@wkwerner> <3459c0fd.1431258@news.playstation.co.uk> <01bce639$f3382a80$78bf43ce@wkwerner> <01bce8db$44ff5fc0$6ebf43ce@wkwerner> NNTP-Posting-Host: onyx0.corp.cubic.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01SC-SGI (X11; I; IRIX 5.3 IP19) wayne a. lee wrote: > > I haven't looked into this, but it occurs to me that using the sample code > in _psstart.c to init the heap could potentially cause overwriting of TMD > data or whatever IF you decided to load such unallocated, hard-coded data > *after* (i.e. in higher memory locations) the code, rather than before. > That was my concern. My data is after my code. With my data stored in hard coded locations, I prefer to have control over heap size and location. David White