public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114416] SPARC V9 struct return with floating-point members violates ABI Date: Thu, 21 Mar 2024 14:54:24 +0000 [thread overview] Message-ID: <bug-114416-4-ZdZ6yxp4Q4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114416-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114416 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2024-03-21 Ever confirmed|0 |1 --- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- IMO that's not clear: "Structure or union types are always left-justified, whether stored in registers or memory. The individual fields of a structure (or containing storage unit in the case of bit fields) are subject to promotion into registers based on their type using the same rules as apply to scalar values (with the addition that a single-precision floating-point number assigned to the left half of an argument slot will be promoted into the corresponding even-numbered float register.). Any union type being passed directly is subject to promotion into the appropriate integer register(s)." I don't see how "The individual fields |...] are subject to promotion into registers based on their type using the same rules as apply to scalar values" applies to an array field, since its type is not scalar. Admittedly, this does not directly apply to a structure field either, but I think that GCC does apply the rule recursively in this case. AFAIK we have never implemented this interpretation for array fields, so I wonder whether it's not too late now.
next prev parent reply other threads:[~2024-03-21 14:54 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-21 13:00 [Bug target/114416] New: " ro at gcc dot gnu.org 2024-03-21 13:00 ` [Bug target/114416] " ro at gcc dot gnu.org 2024-03-21 13:01 ` ro at gcc dot gnu.org 2024-03-21 14:54 ` ebotcazou at gcc dot gnu.org [this message] 2024-03-21 15:08 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-03-24 10:42 ` ebotcazou at gcc dot gnu.org 2024-03-25 9:02 ` [Bug target/114416] calling convention incompatibility with vendor compiler for V9 ebotcazou at gcc dot gnu.org 2024-03-27 9:49 ` jakub.kulik at oracle dot com 2024-03-27 9:56 ` jakub.kulik at oracle dot com 2024-03-27 10:13 ` ebotcazou at gcc dot gnu.org 2024-03-27 10:16 ` ebotcazou at gcc dot gnu.org 2024-04-17 14:06 ` jakub.kulik at oracle dot com 2024-04-17 14:08 ` jakub.kulik at oracle dot com 2024-04-23 8:31 ` ebotcazou at gcc dot gnu.org 2024-04-23 11:34 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-04-24 7:26 ` ebotcazou at gcc dot gnu.org 2024-04-24 7:31 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-04-24 12:17 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-04-24 12:29 ` ebotcazou at gcc dot gnu.org 2024-04-24 12:34 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-04-25 9:29 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-04-25 10:48 ` cvs-commit at gcc dot gnu.org 2024-04-25 10:56 ` ebotcazou at gcc dot gnu.org 2024-04-25 11:01 ` jakub.kulik at oracle dot com
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-114416-4-ZdZ6yxp4Q4@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).