From mint-bounce@lists.fishpool.fi Mon Feb 1 17:00:16 2010 Message-ID: <4B674E4E.4050601@freesbee.fr> Date: Mon, 01 Feb 2010 22:57:34 +0100 From: =?ISO-8859-1?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: <4B6607C7.6090309@freesbee.fr> <4B66183F.6060302@chello.nl> <4B674BBE.8040809@chello.nl> In-Reply-To: <4B674BBE.8040809@chello.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Antivirus: avast! (VPS 100201-0, 01/02/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 o11M0Gh5005622 Henk Robbers wrote: > How does GCC behave? GCC never pushes bytes on the stack. char and shorts are extended to int before being pushed. So if a function takes a char as first argument, in the callee it is located at 7(sp) by default (32-bit ints), or 5(sp) with -mshort (16-bit ints). -- Vincent Rivière