From: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
To: Steve Ellcey <sellcey@marvell.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"jakub@redhat.com" <jakub@redhat.com>,
"Richard Earnshaw" <Richard.Earnshaw@arm.com>,
Richard Sandiford <Richard.Sandiford@arm.com>
Cc: nd <nd@arm.com>
Subject: Re: [PATCH] Fix simd attribute handling on aarch64 (version 2)
Date: Wed, 07 Aug 2019 10:51:00 -0000 [thread overview]
Message-ID: <bb79392d-c864-cb62-9198-8e91ba956867@arm.com> (raw)
In-Reply-To: <mpt4l32hdip.fsf@arm.com>
On 31/07/2019 08:25, Richard Sandiford wrote:
> Steve Ellcey <sellcey@marvell.com> writes:
>>
>> 2019-07-30 Steve Ellcey <sellcey@marvell.com>
>>
>> * omp-simd-clone.c (simd_clone_adjust_return_type): Remove call to
>> build_distinct_type_copy.
>> (simd_clone_adjust_argument_types): Ditto.
>> (simd_clone_adjust): Call build_distinct_type_copy here.
>> (expand_simd_clones): Ditto.
>>
>> 2019-07-30 Steve Ellcey <sellcey@marvell.com>
>>
>> * gcc.target/aarch64/simd_pcs_attribute.c: New test.
>> * gcc.target/aarch64/simd_pcs_attribute-2.c: Ditto.
>> * gcc.target/aarch64/simd_pcs_attribute-3.c: Ditto.
>
> OK if there are no objections in 48 hours.
i think this should be backported to gcc-9 too.
next prev parent reply other threads:[~2019-08-07 10:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 21:29 [PATCH] Fix simd attribute handling on aarch64 Steve Ellcey
2019-07-18 9:22 ` Richard Sandiford
2019-07-18 16:04 ` Steve Ellcey
2019-07-19 15:57 ` [PATCH] Fix simd attribute handling on aarch64 (version 2) Steve Ellcey
2019-07-19 18:26 ` Richard Sandiford
2019-07-22 18:26 ` Steve Ellcey
2019-07-29 23:00 ` Steve Ellcey
2019-07-30 13:35 ` Richard Sandiford
2019-07-30 22:14 ` Steve Ellcey
2019-07-31 7:34 ` Richard Sandiford
2019-08-07 10:51 ` Szabolcs Nagy [this message]
2019-08-07 18:16 ` 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=bb79392d-c864-cb62-9198-8e91ba956867@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Richard.Sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=nd@arm.com \
--cc=sellcey@marvell.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).