public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kyrill Tkachov <kyrylo.tkachov@arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
	 Richard Earnshaw <Richard.Earnshaw@arm.com>,
	James Greenhalgh <James.Greenhalgh@arm.com>
Subject: Re: [PATCH][AArch64] PR target/65491: Classify V1TF vectors as AAPCS64 short vectors rather than composite types
Date: Mon, 18 May 2015 10:09:00 -0000	[thread overview]
Message-ID: <5559B941.8090302@arm.com> (raw)
In-Reply-To: <5551C278.8010701@arm.com>

Ping^3.

Thanks,
Kyrill

On 12/05/15 10:06, Kyrill Tkachov wrote:
> Ping^2.
>
> Thanks,
> Kyrill
>
> On 06/05/15 10:57, Kyrill Tkachov wrote:
>> Ping.
>> https://gcc.gnu.org/ml/gcc-patches/2015-04/msg01004.html
>>
>> Thanks,
>> Kyrill
>>
>> On 20/04/15 11:16, Kyrill 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).
>>>
>>> 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).
>>>
>>> With this patch the testcase compiles fine and in the generated code the
>>> argument is passed
>>> in the simd registers like the ABI requires.
>>>
>>> Bootstrapped and tested on aarch64-linux.
>>>
>>> This bug appears on all release branches so it's not a regression.
>>> Ok for trunk?
>>> Do we want this in the release branches eventually?
>>>
>>> Thanks,
>>> Kyrill
>>>
>>> 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.

  reply	other threads:[~2015-05-18 10:04 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 [this message]
2015-05-19 11:21 ` James Greenhalgh
2015-05-22 14:49   ` Kyrill Tkachov

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=5559B941.8090302@arm.com \
    --to=kyrylo.tkachov@arm.com \
    --cc=James.Greenhalgh@arm.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@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: 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).