From mint-bounce@lists.fishpool.fi Sun Jan 31 17:52:38 2010 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes Subject: Re: [MiNT] how to compile stik/sting stuff with gcc4 References: <4B6607C7.6090309@freesbee.fr> Date: Sun, 31 Jan 2010 23:51:03 +0100 To: "mint@lists.fishpool.fi" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Helmut Karlowski" Message-ID: In-Reply-To: <4B6607C7.6090309@freesbee.fr> User-Agent: Opera Mail/10.10 (Win32) X-Antivirus: avast! (VPS 100131-1, 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: helmut.karlowski@ish.de Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Am 31.01.2010, 23:44 Uhr, schrieb Vincent Rivière : > 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. And if Coldfire really does this then gcc and any other compiler should not use this instruction. I hope it's done this way already. -- Helmut Karlowski