[Bug target/110188] gcc for RISC-V stack aligned error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110188 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/110188] gcc for RISC-V stack aligned error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110188 --- Comment #6 from jzhgonha at 163 dot com --- thank you very much! 发自我的小米在 "kito at gcc dot gnu.org" ，2023年6月9日 下午9:51写道： https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110188 Kito Cheng changed: What |Removed |Added

[Bug target/110188] gcc for RISC-V stack aligned error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110188 Kito Cheng changed: What|Removed |Added CC||kito at gcc dot gnu.org --- Comment #5 fro

[Bug target/110188] gcc for RISC-V stack aligned error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110188 --- Comment #4 from 18761437418 at 163 dot com --- thank you very much. according to the define, STACK_BOUNDARY is 8 bytes, ABI_STACK_BOUNDARY is 128, just 16bytes, not 32bytes, but compiler allocate 32bytes to stack. At 2023-06-09

[Bug target/110188] gcc for RISC-V stack aligned error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110188 --- Comment #3 from Andreas Schwab --- According to riscv.h there is a difference between ABI and calling conventions: /* The smallest supported stack boundary the calling convention supports. */ #define STACK_BOUNDARY \ (riscv_abi == ABI_IL

[Bug target/110188] gcc for RISC-V stack aligned error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110188 --- Comment #2 from 18761437418 at 163 dot com --- thank you very much, I have tried different optimization levels, but all occupy 32bytes. O0, O1, O2, O3, Os all occupy 32bytes. comand: riscv64-unknown-elf-gcc -c main.c -o main.o -march=rv32ima

[Bug target/110188] gcc for RISC-V stack aligned error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110188 --- Comment #1 from Andrew Pinski --- This is at -O0. Maybe -O1 or -O2 will use the reduced stack size.