From mint-bounce@lists.fishpool.fi Thu Aug 11 08:44:22 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Date: Thu, 11 Aug 2005 08:41:39 +0200 From: mikro To: Andreas Schwab Cc: Mint list Subject: Re: [MiNT] what's wrong with this code? Message-ID: <20050811064139.GA16995@hysteria.sk> References: <20050810084953.GA29857@hysteria.sk> <42F9C8C7.6040602@klockars.net> <20050810100104.GB29857@hysteria.sk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: mikro@hysteria.sk Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00 X-Spam-Level: > Check out VBR. It might be non-zero. > nice tip, however, it doesn't help. I've tried replacing it with the simple Super() call, still no success. So I guess there's something bad with MiNT's exception/process handling because if I remove everything between move from a7 and to a7, it works. If I use just small loop (30-40 cycles) which use this a7, it works let's say 10 seconds. And if I use long loop (thousands of cycles) it freezes very fast. -- --------------------------------------------------------------------------- MiKRO Atari XE/XL/Mega STE/Falcon060 http://mikro.atari.org ---------------------------------------------------------------------------