- This optimization will adjust stack, but it not check/update other
stack pointer use-site, the example is when the arguments put on
stack, the offset become wrong after optimization.
- However adjust stack frame usage after register allocation could be
error prone, so we decide to turn off this optimization for such case.
- Ye-Ting Kuo report this issue on github:
https://github.com/riscv/riscv-gcc/pull/192
gcc/ChangeLog:
* config/riscv/riscv-sr.c (riscv_remove_unneeded_save_restore_calls):
Abort if any arguments on stack.
gcc/testsuite/ChangeLog
* gcc.target/riscv/save-restore-9.c: New.
void
riscv_remove_unneeded_save_restore_calls (void)
{
+ /* We'll adjust stack size after this optimization, that require update every
+ sp use site, which could be unsafe, so we decide to turn off this
+ optimization if there are any arguments put on stack. */
+ if (crtl->args.size != 0)
+ return;
+
/* Will point to the first instruction of the function body, after the
prologue end note. */
rtx_insn *body = NULL;
--- /dev/null
+/* { dg-do run } */
+/* { dg-options "-O2 -msave-restore" } */
+
+int
+__attribute__((noinline,noclone))
+foo (int u)
+{
+ return u + 1;
+}
+
+int
+__attribute__((noinline,noclone))
+bar (int a, int b, int c, int d, int e, int f, int g, int h, int u)
+{
+ return foo (u);
+}
+
+int main()
+{
+ if (bar (1, 2, 3, 4, 5, 6, 7, 8, 9) != 10)
+ __builtin_abort();
+ return 0;
+}