On Tue, Sep 1, 2009 at 12:31 PM, Ian Lance Taylor wrote:
> Godmar Back writes:
>
>> It appears to me that '-mno-push-args' is the enabled by default (*),
>> and not '-mpush-args'.
>
> The default varies by processor--it dependson the -mtune option.
I don't know how to find out which tuning is ena
Godmar Back writes:
> It appears to me that '-mno-push-args' is the enabled by default (*),
> and not '-mpush-args'.
The default varies by processor--it dependson the -mtune option.
> Moreover, since -maccumulate-outgoing-args
> implies -mno-push-args, it appears that the only way to obtain
> '
Minor correction to my previous email:
On Tue, Sep 1, 2009 at 10:08 AM, Godmar Back wrote:
>
> gb...@setzer [39](~/tmp) > cat call.c
> void caller(void) {
> extern void callee(int);
> callee(5);
> }
This:
> gb...@setzer [40](~/tmp) > gcc -mno-push-args -S call.c
should be '-mpush-args' as
Hi,
I'm using gcc version 4.1.2 20080704 (Red Hat 4.1.2-44) for a x86
target. The info page says:
`-mpush-args'
`-mno-push-args'
Use PUSH operations to store outgoing parameters. This method is
shorter and usually equally fast as method using SUB/MOV
operations and is enabled by d
