From mint-bounce@lists.fishpool.fi Mon Feb 1 16:49:40 2010 X-SourceIP: 77.249.76.7 Message-ID: <4B674BBE.8040809@chello.nl> Date: Mon, 01 Feb 2010 22:46:38 +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> <4B66183F.6060302@chello.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Miro Kropacek wrote: >>AHCC widens a char parameter to its 16 bit equivalent before pushing. >> > > Hmm if AHCC does something like ext.w d0; move.w d0,-(sp) it breaks PureC > ABI, doesn't it? I've just checked it, move.b d0,-(sp) stores char value and > then reserve empty space, not vice versa. > 'ABI' is too loud a statement for such things. I didnt even know Pure C behaves like this until this thread. How does GCC behave? -- 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