public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109435] overaligned structs are not passed correctly for mips64 Date: Fri, 30 Jun 2023 03:21:15 +0000 [thread overview] Message-ID: <bug-109435-4-pqYC7NiSZe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109435-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109435 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by YunQiang Su <syq@gcc.gnu.org>: https://gcc.gnu.org/g:e20abdb749d0c0c8552da998ff8ec139b830f5eb commit r14-2205-ge20abdb749d0c0c8552da998ff8ec139b830f5eb Author: Jovan Dmitrovic <Jovan.Dmitrovic@Syrmia.com> 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Ä <jovan.dmitrovic@syrmia.com> 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.
next prev parent reply other threads:[~2023-06-30 3:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-06 14:04 [Bug other/109435] New: [MIPS64R6] Typedef struct alignment returns incorrect results jovan.dmitrovic at syrmia dot com 2023-04-06 14:28 ` [Bug other/109435] " jovan.dmitrovic at syrmia dot com 2023-04-06 19:14 ` [Bug target/109435] overaligned structs are not passed correctly for mips64 pinskia at gcc dot gnu.org 2023-05-29 11:07 ` jovan.dmitrovic at syrmia dot com 2023-06-30 3:21 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-01 6:35 ` syq at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-109435-4-pqYC7NiSZe@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).