[Bug target/109435] overaligned structs are not passed correctly for mips64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109435 YunQiang Su changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||syq at gcc dot gnu.org --- Comment #5 from YunQiang Su --- Fixed by commit: https://gcc.gnu.org/g:e20abdb749d0c0c8552da998ff8ec139b830f5eb
[Bug target/109435] overaligned structs are not passed correctly for mips64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109435 --- Comment #4 from CVS Commits --- The master branch has been updated by YunQiang Su : https://gcc.gnu.org/g:e20abdb749d0c0c8552da998ff8ec139b830f5eb commit r14-2205-ge20abdb749d0c0c8552da998ff8ec139b830f5eb Author: Jovan Dmitrovic Date: Mon Jun 26 17:00:20 2023 +0200 mips: Fix overaligned function arguments [PR109435] This patch changes alignment for typedef types when passed as arguments, making the alignment equal to the alignment of original (aliased) types. This change makes it impossible for a typedef type to have alignment that is less than its size. 2023-06-27 Jovan DmitroviÄ gcc/ChangeLog: PR target/109435 * config/mips/mips.cc (mips_function_arg_alignment): Returns the alignment of function argument. In case of typedef type, it returns the aligment of the aliased type. (mips_function_arg_boundary): Relocated calculation of the aligment of function arguments. gcc/testsuite/ChangeLog: * gcc.target/mips/align-1-n64.c: New test. * gcc.target/mips/align-1-o32.c: New test.
[Bug target/109435] overaligned structs are not passed correctly for mips64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109435 --- Comment #3 from Jovan Dmitrović --- Tentative patch posted on the mailing list: https://gcc.gnu.org/pipermail/gcc-patches/2023-May/619949.html
[Bug target/109435] overaligned structs are not passed correctly for mips64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109435 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill ||a/show_bug.cgi?id=88469 --- Comment #2 from Andrew Pinski --- The aarch64 and arm backends had a similar issue which was fixed too.