From mint-bounce@lists.fishpool.fi Sun Jan 31 17:47:36 2010 Message-ID: <4B6607C7.6090309@freesbee.fr> Date: Sun, 31 Jan 2010 23:44:23 +0100 From: =?ISO-8859-15?Q?Vincent_Rivi=E8re?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] how to compile stik/sting stuff with gcc4 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15; format=flowed X-Antivirus: avast! (VPS 100131-0, 31/01/2010), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o0VMlaut028597 Helmut Karlowski wrote: >> instructions. I'm unsure only about one thing and that is "move.b >> d0,-(sp)" >> and following stack restore -- on m68k, this increases stack with +2, >> on CF >> (IIRC) only +1 so the stack gets corrupted. > > Do you mean 68000 with m68k or 680x0? If I'm not wrong this is a difference between the 680x0 family and ColdFire family. All 680x0 models should behave the same way on move.b xx,-(sp) This could be easily checked on real hardware. -- Vincent Rivière