From mint-bounce@lists.fishpool.fi Sun Jan 31 18:56:52 2010 X-SourceIP: 77.249.76.7 Message-ID: <4B66183F.6060302@chello.nl> Date: Mon, 01 Feb 2010 00:54:39 +0100 From: Henk Robbers User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "mint@lists.fishpool.fi" Subject: Re: [MiNT] how to compile stik/sting stuff with gcc4 References: <4B6607C7.6090309@freesbee.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: h.robbers@chello.nl Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Helmut Karlowski wrote: > 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. > AHCC widens a char parameter to its 16 bit equivalent before pushing. I consider the way Pure C behaves as a bug (or at least a mistake). -- Groeten; Regards. Henk Robbers. http://members.chello.nl/h.robbers Interactive disassembler: TT-Digger; http://digger.atari.org A Home Cooked C compiler: AHCC; http://ahcc.atari.org