From: Kyrill Tkachov <kyrylo.tkachov@arm.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PATCH][AArch64] PR target/65491: Classify V1TF vectors as AAPCS64 short vectors rather than composite types
Date: Fri, 22 May 2015 14:49:00 -0000 [thread overview]
Message-ID: <555F3F9D.8000002@arm.com> (raw)
In-Reply-To: <20150519111854.GA31361@arm.com>
Hi James,
On 19/05/15 12:18, James Greenhalgh wrote:
> On Mon, Apr 20, 2015 at 11:16:02AM +0100, Kyrylo Tkachov wrote:
>> Hi all,
>>
>> The ICE in the PR happens when we pass a 1x(128-bit float) vector as an
>> argument.
>> The aarch64 backend erroneously classifies it as a composite type when in
>> fact it
>> is a short vector according to AAPCS64
>> (section 4.1.2 from
>> http://infocenter.arm.com/help/topic/com.arm.doc.ihi0055b/IHI0055B_aapcs64.p
>> df).
> Agreed.
>
>> The solution in this patch is to check aarch64_composite_type_p for a short
>> vector with
>> aarch64_short_vector_p rather than the other way around (check for
>> aarch64_short_vector_p
>> in aarch64_composite_type_p).
> I think I understand what you are saying, but your patch does the
> opposite (ADDS a check for aarch64_short_vector_p in
> aarch64_composite_type_p, REMOVES a check for aarch64_composite_type_p,
> in aarch64_short_vector_p)...
Yeah, I just worded it wrong in the cover letter, sorry about that.
As you say, the logic is pretty hairy.
>
> This logic is pretty hairy, and I'm struggling to convince myself that
> your change only hits the bug you described above. I think I've worked
> it through and it does, but if you can find any additional ABI tests
> which stress the Vector/Floating-Point passing rules that would help
> settle my nerves.
The aapcs64.exp stuff seems to test the existing rules
quite well...
>
> The patch is OK. I wouldn't think we would want to backport it to
> release branches as there is no regression to fix.
Ok, I've committed it with r223577.
I agree that it's not a regression fix, so messing with ABI code
in the release branches is not desirable.
Thanks for the review.
Kyrill
>
> Thanks,
> James
>
>> 2015-04-20 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
>>
>> PR target/65491
>> * config/aarch64/aarch64.c (aarch64_short_vector_p): Move above
>> aarch64_composite_type_p. Remove check for aarch64_composite_type_p.
>> (aarch64_composite_type_p): Return false if given type and mode are
>> for a short vector.
>>
>> 2015-04-20 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
>>
>> PR target/65491
>> * gcc.target/aarch64/pr65491_1.c: New test.
>> * gcc.target/aarch64/aapcs64/type-def.h (vlf1_t): New typedef.
>> * gcc.target/aarch64/aapcs64/func-ret-1.c: Add test for vlf1_t.
prev parent reply other threads:[~2015-05-22 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 10:16 Kyrill Tkachov
2015-05-06 9:58 ` Kyrill Tkachov
2015-05-12 9:07 ` Kyrill Tkachov
2015-05-18 10:09 ` Kyrill Tkachov
2015-05-19 11:21 ` James Greenhalgh
2015-05-22 14:49 ` Kyrill Tkachov [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=555F3F9D.8000002@arm.com \
--to=kyrylo.tkachov@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.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).