From: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
To: "sellcey@cavium.com" <sellcey@cavium.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: nd <nd@arm.com>
Subject: Re: [Patch 1/4][Aarch64] v2: Implement Aarch64 SIMD ABI
Date: Wed, 13 Feb 2019 16:54:00 -0000 [thread overview]
Message-ID: <62101b5b-3ec3-6ebe-baa5-d1a85ccf3ab2@arm.com> (raw)
In-Reply-To: <1541699539.12016.6.camel@cavium.com>
On 08/11/2018 17:52, Steve Ellcey wrote:
> This is a resubmission of patch 1 to support the Aarch64 SIMD ABI [1] in
> GCC, it does not have any functional changes from the last submit.
>
> The significant difference between the standard ARM ABI and the SIMD ABI
> is that in the normal ABI a callee saves only the lower 64 bits of registers
> V8-V15, in the SIMD ABI the callee must save all 128 bits of registers
> V8-V23.
...
> --- a/gcc/config/aarch64/aarch64.c
> +++ b/gcc/config/aarch64/aarch64.c
> @@ -1088,6 +1088,15 @@ static const struct processor *selected_tune;
> /* The current tuning set. */
> struct tune_params aarch64_tune_params = generic_tunings;
>
> +/* Table of machine attributes. */
> +static const struct attribute_spec aarch64_attribute_table[] =
> +{
> + /* { name, min_len, max_len, decl_req, type_req, fn_type_req,
> + affects_type_identity, handler, exclude } */
> + { "aarch64_vector_pcs", 0, 0, false, true, true, false, NULL, NULL },
i just noticed that "affects_type_identity" is set to false,
so gcc accepts
__attribute__((aarch64_vector_pcs)) void f(void);
void (*g)(void) = f;
without a warning (treats function types with different
pcs as compatible)
i think we don't want to allow calls through the wrong
pointer type, such assignment should be an error.
next prev parent reply other threads:[~2019-02-13 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 17:52 Steve Ellcey
2018-12-07 17:34 ` Richard Sandiford
2018-12-11 23:01 ` Steve Ellcey
2018-12-12 11:39 ` Richard Sandiford
2018-12-12 18:26 ` [EXT] " Steve Ellcey
2018-12-12 18:49 ` Richard Sandiford
2019-02-13 16:54 ` Szabolcs Nagy [this message]
2019-02-13 17:24 ` Steve Ellcey
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=62101b5b-3ec3-6ebe-baa5-d1a85ccf3ab2@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.com \
--cc=sellcey@cavium.com \
/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: link
Be 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).