public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "michael.hudson at linaro dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59799] New: aarch64_pass_by_reference never passes arrays by value, contrary to ABI documentation Date: Tue, 14 Jan 2014 01:59:00 -0000 [thread overview] Message-ID: <bug-59799-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59799 Bug ID: 59799 Summary: aarch64_pass_by_reference never passes arrays by value, contrary to ABI documentation Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: michael.hudson at linaro dot org It's always possible I'm totally misunderstanding something here, but it seems that this code: /* Arrays always passed by reference. */ if (TREE_CODE (type) == ARRAY_TYPE) return true; in gcc/config/aarch64/aarch64.c does not agree with the rules from "Procedure Call Standard for the ARM 64-bit Architecture" (http://infocenter.arm.com/help/topic/com.arm.doc.ihi0055b/IHI0055B_aapcs64.pdf). As far as I can see the rules on page 18 and 19 make no distinction between arrays and structs and they can both be passed in registers when small enough.
next reply other threads:[~2014-01-14 1:59 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-14 1:59 michael.hudson at linaro dot org [this message] 2014-01-14 2:04 ` [Bug target/59799] " pinskia at gcc dot gnu.org 2014-01-14 2:05 ` pinskia at gcc dot gnu.org 2014-01-14 2:06 ` ian at airs dot com 2014-01-15 0:48 ` pinskia at gcc dot gnu.org 2014-01-15 9:04 ` ebotcazou at gcc dot gnu.org 2014-01-16 22:19 ` michael.hudson at linaro dot org 2014-01-17 1:43 ` michael.hudson at linaro dot org 2014-01-17 4:51 ` ian at airs dot com 2014-01-17 18:19 ` yufeng at gcc dot gnu.org 2014-02-19 15:33 ` yroux at gcc dot gnu.org 2014-10-27 15:24 ` ramana at gcc dot gnu.org 2014-10-27 20:25 ` michael.hudson at linaro dot 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-59799-4@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).