From mint-bounce@lists.fishpool.fi Mon Apr 27 14:17:49 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=0LDCrafV56FeH8w1fpRXql28QnXlzdK69+GzuvFRxZk=; b=wM63A10KJ2V0HUtMtX2QW7yfeh0syelZNC9FM5Or67BFzq+fg+P+SLXvM5k1VroKhq Uy66rJxiQKRScuXxC6/qMDKppXiZsLAYxtaDXsehg4OyMIWj4YN/NEHeYk/eHJLsfTNg CGvsMIvf/sLqw4kRIZeEcCkiNG0qpWCY5cJLQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=E1gVxhOVYjjb6mYn49YwDv0hk9Qic5ggjYeo0qBPXg2EpDc81lByOQmUOuRvLl8mp0 hd7gjvBwhBsMuLWIKYXT3HcVB8gov7F8M8cfeLimuwmCQXwLlUUeqUx/k0Yg5kuKLNKU RSlDf2Kr7QdSGeisO5tKt0JCX9XCj102mGKLo= MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 27 Apr 2009 20:12:14 +0200 Message-ID: Subject: Re: [MiNT] Possible MintLib FastRAM bug in TOS/MagiC? (Or My Own Error...) From: Miro Kropacek To: Keith Scroggins Cc: mint@fishpool.com Content-Type: multipart/alternative; boundary=000e0cd244923424e304688d49d2 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: miro.kropacek@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: --000e0cd244923424e304688d49d2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, This is the -a flag (set the fast ram allocation flag)? Removing that bit > should help, or most likely will not make a difference? (I will try it when > I get home, along with GCC 4.4.0). I'm not sure, what "-a" ? When you take a look at Mxalloc() parameters, there's one where you set if it's ST/TT RAM. And in this mode you can specify bit #3 as "use mint memory model". I do know the out of memory is happening in a calloc call, which I am > guessing (and I could be totally wrong) is being converted to a mxalloc in > TOS. This call does work when less memory is needed/used. The important thing is if it uses that bit. The bit is used for example for global memory allocation (for VA/d&d protocol for example). -- MiKRO / Mystic Bytes http://mikro.atari.org --000e0cd244923424e304688d49d2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

This is the -a flag (set the fast ram allocation flag)= ? =A0Removing that bit should help, or most likely will not make a differen= ce? (I will try it when I get home, along with GCC 4.4.0).
I'm not sure, what "-a" ? When you take a look at Mxallo= c() parameters, there's one where you set if it's ST/TT RAM. And in= this mode you can specify bit #3 as "use mint memory model".

I do kn= ow the out of memory is happening in a calloc call, which I am guessing (an= d I could be totally wrong) is being converted to a mxalloc in TOS. =A0This= call does work when less memory is needed/used.
The important thing is if it uses that bit. The bit is used for exampl= e for global memory allocation (for VA/d&d protocol for example).

--
MiKRO / Mystic Bytes
http://mikro.atari.org
--000e0cd244923424e304688d49d2--