为什么gcc使用movl而不是push来传递函数参数？

发布于 2024-10-08 21:44:10 字数 500 浏览 10 评论 0原文

注意这段代码：

#include <stdio.h>
void a(int a, int b, int c)
{
    char buffer1[5];
    char buffer2[10];
}

int main()
{
    a(1,2,3); 
}

之后：

gcc -S a.c

该命令显示了我们的汇编源代码。

现在我们可以看到在主函数中，我们从不使用“push”命令来推送参数将a函数放入栈中。它使用“移动”而不是

main:
 pushl %ebp
 movl %esp, %ebp
 andl $-16, %esp
 subl $16, %esp
 movl $3, 8(%esp)
 movl $2, 4(%esp)
 movl $1, (%esp)
 call a
 leave

为什么会发生这种情况？他们之间有什么区别？

原文

pay attention to this code :

#include <stdio.h>
void a(int a, int b, int c)
{
    char buffer1[5];
    char buffer2[10];
}

int main()
{
    a(1,2,3); 
}

after that :

gcc -S a.c

that command shows our source code in assembly.

now we can see in the main function, we never use "push" command to push the arguments of
the a function into the stack. and it used "movel" instead of that

main:
 pushl %ebp
 movl %esp, %ebp
 andl $-16, %esp
 subl $16, %esp
 movl $3, 8(%esp)
 movl $2, 4(%esp)
 movl $1, (%esp)
 call a
 leave

why does it happen?
what's difference between them?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

对风讲故事 2024-10-15 21:44:10

这是gcc手册不得不说一下：

-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 default. 
    In some cases disabling it may improve performance because of improved scheduling
    and reduced dependencies.

 -maccumulate-outgoing-args
    If enabled, the maximum amount of space required for outgoing arguments will be
    computed in the function prologue. This is faster on most modern CPUs because of
    reduced dependencies, improved scheduling and reduced stack usage when preferred
    stack boundary is not equal to 2. The drawback is a notable increase in code size.
    This switch implies -mno-push-args.

显然 -maccumulate-outgoing-args 默认情况下启用，覆盖 -mpush-args。使用 -mno-accumulate-outgoing-args 显式编译确实会恢复为 PUSH 方法（此处）。

2019 更新：自 Pentium M 以来，现代 CPU 已实现高效的入栈/出栈。
-mno-accumulate-outgoing-args（并使用推送）最终在 2014 年 1 月成为 -mtune=generic 的默认设置。

Here is what the gcc manual has to say about it:

-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 default. 
    In some cases disabling it may improve performance because of improved scheduling
    and reduced dependencies.

 -maccumulate-outgoing-args
    If enabled, the maximum amount of space required for outgoing arguments will be
    computed in the function prologue. This is faster on most modern CPUs because of
    reduced dependencies, improved scheduling and reduced stack usage when preferred
    stack boundary is not equal to 2. The drawback is a notable increase in code size.
    This switch implies -mno-push-args.

Apparently -maccumulate-outgoing-args is enabled by default, overriding -mpush-args. Explicitly compiling with -mno-accumulate-outgoing-args does revert to the PUSH method, here.

2019 update: modern CPUs have had efficient push/pop since about Pentium M.
-mno-accumulate-outgoing-args (and using push) eventually became the default for -mtune=generic in Jan 2014.

回复收藏 0 原文

断肠人 2024-10-15 21:44:10

该代码只是直接将常量 (1, 2, 3) 放置在距（更新的）堆栈指针 (esp) 的偏移位置处。编译器选择手动执行“推送”，但结果相同。

“push”既设置数据又更新堆栈指针。在这种情况下，编译器将其减少为仅对堆栈指针进行一次更新（而不是三次）。一项有趣的实验是尝试更改函数“a”以仅采用一个参数，并查看指令模式是否发生变化。

回复收藏 0 原文

清风疏影 2024-10-15 21:44:10

gcc 进行各种优化，包括根据要优化的特定 CPU 的执行速度来选择指令。您会注意到像 x *= n 这样的东西经常被 SHL、ADD 和/或 SUB 的混合所取代，特别是当 n 是常数时；而 MUL 仅在 SHL-ADD-SUB 组合的平均运行时间（以及缓存等占用空间）超过 MUL 时使用，或者 n 不是常量（因此使用循环）使用 shl-add-sub 会更昂贵）。

对于函数参数：MOV 可以由硬件并行化，而 PUSH 则不能。（由于 esp 寄存器的更新，第二个 PUSH 必须等待第一个 PUSH 完成。）在函数参数的情况下，MOV 可以并行运行。

回复收藏 0 原文