From: Richard Sandiford <richard.sandiford@arm.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] aarch64, acle header: Cast uint64_t pointers to DIMode.
Date: Mon, 19 Feb 2024 09:48:43 +0000 [thread overview]
Message-ID: <mptbk8cpyx0.fsf@arm.com> (raw)
In-Reply-To: <B80FA858-409F-42E7-B793-8A0C86BA74BB@sandoe.co.uk> (Iain Sandoe's message of "Fri, 16 Feb 2024 13:40:55 +0000")
Iain Sandoe <iain@sandoe.co.uk> writes:
>> On 15 Feb 2024, at 18:05, Richard Sandiford <richard.sandiford@arm.com> wrote:
>>
>> Iain Sandoe <iains.gcc@gmail.com> writes:
>>>> On 5 Feb 2024, at 14:56, Iain Sandoe <iains.gcc@gmail.com> wrote:
>>>>
>>>> Tested on aarch64-linux,darwin and a cross from aarch64-darwin to linux,
>>>> OK for trunk, or some alternative is needed?
>>>
>>> Hmm.. apparently, this fails the linaro pre-commit CI for g++ with:
>>> error: invalid conversion from 'long int*' to 'long unsigned int*' [-fpermissive]
>>>
>>> So, I guess some alternative is needed, advice welcome,
>>
>> The builtins are registered with:
>>
>> static void
>> aarch64_init_rng_builtins (void)
>> {
>> tree unsigned_ptr_type = build_pointer_type (unsigned_intDI_type_node);
>> ...
>>
>> Does it work if you change unsigned_intDI_type_node to
>> get_typenode_from_name (UINT64_TYPE)?
>
> Yes, that works fine; tested on aarch64-linux and aarch64-darwin.
>
> revised, as below,
> OK for trunk?
> Iain
>
>
> Subject: [PATCH] aarch64: Register rng builtins with uint64_t pointers.
>
> Currently, these are registered as unsigned_intDI_type_node which is not
> necessarily the same type definition as uint64_t. On platforms where these
> differ that causes fails in consuming the arm_acle.h header.
>
> gcc/ChangeLog:
>
> * config/aarch64/aarch64-builtins.cc (aarch64_init_rng_builtins):
> Register these builtins with a pointer to uint64_t rather than unsigned
> DI mode.
OK, thanks.
Richard
> ---
> gcc/config/aarch64/aarch64-builtins.cc | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/gcc/config/aarch64/aarch64-builtins.cc b/gcc/config/aarch64/aarch64-builtins.cc
> index e211a7271ba..1330558f109 100644
> --- a/gcc/config/aarch64/aarch64-builtins.cc
> +++ b/gcc/config/aarch64/aarch64-builtins.cc
> @@ -1759,7 +1759,8 @@ aarch64_init_tme_builtins (void)
> static void
> aarch64_init_rng_builtins (void)
> {
> - tree unsigned_ptr_type = build_pointer_type (unsigned_intDI_type_node);
> + tree unsigned_ptr_type
> + = build_pointer_type (get_typenode_from_name (UINT64_TYPE));
> tree ftype
> = build_function_type_list (integer_type_node, unsigned_ptr_type, NULL);
> aarch64_builtin_decls[AARCH64_BUILTIN_RNG_RNDR]
prev parent reply other threads:[~2024-02-19 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 14:56 Iain Sandoe
2024-02-05 21:04 ` Iain Sandoe
2024-02-15 18:05 ` Richard Sandiford
2024-02-16 13:40 ` Iain Sandoe
2024-02-19 9:48 ` Richard Sandiford [this message]
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=mptbk8cpyx0.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
/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).