From: Jeff Law <law@redhat.com>
To: Ilya Enkovich <enkovich.gnu@gmail.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Cc: Christophe Lyon <christophe.lyon@linaro.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Boolean Vector, patch 1/5] Introduce boolean vector to be used as a vector comparison type
Date: Mon, 02 Nov 2015 19:41:00 -0000 [thread overview]
Message-ID: <5637BC60.4050702@redhat.com> (raw)
In-Reply-To: <20151029130803.GB63456@msticlxl57.ims.intel.com>
On 10/29/2015 07:08 AM, Ilya Enkovich wrote:
> On 28 Oct 22:37, Ilya Enkovich wrote:
>> Seems the problem occurs in this check in expand_vector_operations_1:
>>
>> /* A scalar operation pretending to be a vector one. */
>> if (VECTOR_BOOLEAN_TYPE_P (type)
>> && !VECTOR_MODE_P (TYPE_MODE (type))
>> && TYPE_MODE (type) != BLKmode)
>> return;
>>
>> This is to filter out scalar operations on boolean vectors.
>> The problem here is that TYPE_MODE (type) doesn't return
>> V4SImode assigned to the type but calls vector_type_mode
>> instead which tries to find an integer mode for it and returns
>> TImode. This causes function exit and we don't expand vector
>> comparison.
>>
>> Suppose simple option to fix it is to change default get_mask_mode
>> hook to return BLKmode in case chosen integer vector mode is not
>> vector_mode_supported_p.
>>
>> Thanks,
>> Ilya
>>
>
> Here is a patch which fixes the problem on ARM (and on i386 with -mno-sse also). I checked it fixes the problem on ARM and also bootstrapped and checked it on x86_64-unknown-linux-gnu. Is it OK?
>
> Thanks,
> Ilya
> --
> gcc/
>
> 2015-10-29 Ilya Enkovich <enkovich.gnu@gmail.com>
>
> * targhooks.c (default_get_mask_mode): Use BLKmode in
> case target doesn't support required vector mode.
> * stor-layout.c (layout_type): Check for BLKmode.
VOIDmode would probably be a better choice than BLKmode to signal when
the target doesn't support the required vector mode.
Jeff
next prev parent reply other threads:[~2015-11-02 19:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 13:59 Ilya Enkovich
2015-10-09 20:43 ` Jeff Law
2015-10-13 13:17 ` Richard Biener
2015-10-13 13:35 ` Ilya Enkovich
2015-10-13 13:17 ` Ilya Enkovich
2015-10-22 10:24 ` Andreas Schwab
2015-10-22 10:35 ` Ilya Enkovich
2015-10-22 10:51 ` Andreas Schwab
2015-10-22 16:24 ` Ilya Enkovich
2015-10-22 16:45 ` Jeff Law
2015-10-23 9:43 ` Richard Biener
2015-10-23 11:13 ` Ilya Enkovich
2015-10-23 12:57 ` Richard Biener
2015-10-28 13:55 ` Christophe Lyon
2015-10-28 16:54 ` Bill Schmidt
2015-10-28 19:39 ` Ilya Enkovich
2015-10-29 13:13 ` Ilya Enkovich
2015-11-02 19:41 ` Jeff Law [this message]
2015-11-03 11:26 ` Richard Biener
2015-11-03 13:42 ` Jeff Law
2015-11-03 16:02 ` Jeff Law
2015-10-28 14:57 ` James Greenhalgh
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=5637BC60.4050702@redhat.com \
--to=law@redhat.com \
--cc=christophe.lyon@linaro.org \
--cc=enkovich.gnu@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=wschmidt@linux.vnet.ibm.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).