tree ae7c176eb0141e41c05e17d5eb7f4c998fc7da16
parent 64082912a500d004c53ad1b3425098b495572663
author Nuko Y. <or@dmc.chat> 1747087828 +0000
committer GitHub <noreply@github.com> 1747087828 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJoInHUCRC1aQ7uu5UhlAAASo8QAIBBdeYwbNkojJuDJiEPMkFI
 qIoR4RvwePG/BwaJOZsQpY9hWHDBHfF7GBWjwKFFLo0wZHbkLxtwsegM4fKk82MI
 dRLgZ8SFUZMHoZwiGfUT+V5NX+yWvpCKhN4ZLUfL7M/qmIScmHoC/muD29CftIPt
 t2e6EL+m6lI+rCtwxIRAYox4plqgOArhGogv0q9WE5pLj2j0GO6Nk6JtlaAxQpAQ
 lAMnuwKvFbXkOOWsmAVL6fH9Q/RnIh+YyQeoHGUklPYeXUVTpB12B9n+FA8U5S/v
 RGJrp2JcbO/RBz+rzCgpX4u9beGNMkY+anQ8nqdsP2WYaiu5Gv3kCdraZS3ltfEz
 Llkl6hPpa1FAgeclQ0qbvHk58B9xndSGmn4e8HGnYJ91d5c/dWINuezDzOxyghqR
 RqitsaVStMjPmsv1PpTbAOckGlEaexQZ5GWSI5KuM7sIzDOAcFPu1Pjw84/zHeSj
 SKpo3Ww5BhY2iD8hgXm6gmFx7d8LP1MXLf7lPctaiCQ7We8VCMv+72DQXzs6fZdK
 NYErhQx3T+o+/ALNZB2tfWLOmRGFfju50gp6AgtwmYtcUs6MwbM98Mga4AoDrAiW
 9E773cWcx7HYpQ30MKH+WURLwP/DipPGZxVpN9GB9ynlITI4Jp8Bhwo6RWhNWh02
 DvkmdXkQs4ACXWqhCuXe
 =s7KH
 -----END PGP SIGNATURE-----
 

[AArch64] Stop reserved registers from being saved in prolog/epilog (#138448)

[GCC's
documentation](https://gcc.gnu.org/onlinedocs/gcc-15.1.0/gcc/Code-Gen-Options.html)
is clear on how -ffixed-reg must behave:
```
  Treat the register named reg as a fixed register; generated
  code should never refer to it (except perhaps as a stack pointer,
  frame pointer or in some other fixed role).
```

This implies prolog/epilog code also must not save/restore explicitly
fixed registers, even when it is callee-saved. Some projects rely on
this (GCC's) behavior.

For example,
```
void f() {
  register uint64_t x28 asm("x28") = 0xee;
  asm volatile("" : "+r"(x28)); // avoid mov being eliminated
}
```
should not touch x28 outside of `mov w28,#0xee`.

For riscv64, clang behaves the same as GCC, so I am inclined to believe
this is indeed a bug.

Fixes #111379.