From: Ilya Enkovich <enkovich.gnu@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Yuri Rumyantsev <ysrumyan@gmail.com>, Jeff Law <law@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Igor Zamyatin <izamyatin@gmail.com>
Subject: Re: [PATCH] Simple optimization for MASK_STORE.
Date: Tue, 10 Nov 2015 14:56:00 -0000 [thread overview]
Message-ID: <CAMbmDYYdqVRLorQT1VcS0rJON-ugvU-bFdFRb5y_K_AJNJoYDA@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc0tEYsO44260xNSc0S14QPzog9H8o4uSLxKon0NCAsB9Q@mail.gmail.com>
2015-11-10 17:46 GMT+03:00 Richard Biener <richard.guenther@gmail.com>:
> On Tue, Nov 10, 2015 at 1:48 PM, Ilya Enkovich <enkovich.gnu@gmail.com> wrote:
>> 2015-11-10 15:33 GMT+03:00 Richard Biener <richard.guenther@gmail.com>:
>>> On Fri, Nov 6, 2015 at 2:28 PM, Yuri Rumyantsev <ysrumyan@gmail.com> wrote:
>>>> Richard,
>>>>
>>>> I tried it but 256-bit precision integer type is not yet supported.
>>>
>>> What's the symptom? The compare cannot be expanded? Just add a pattern then.
>>> After all we have modes up to XImode.
>>
>> I suppose problem may be in:
>>
>> gcc/config/i386/i386-modes.def:#define MAX_BITSIZE_MODE_ANY_INT (128)
>>
>> which doesn't allow to create constants of bigger size. Changing it
>> to maximum vector size (512) would mean we increase wide_int structure
>> size significantly. New patterns are probably also needed.
>
> Yes, new patterns are needed but wide-int should be fine (we only need to create
> a literal zero AFACS). The "new pattern" would be equality/inequality
> against zero
> compares only.
Currently 256bit integer creation fails because wide_int for max and
min values cannot be created.
It is fixed by increasing MAX_BITSIZE_MODE_ANY_INT, but it increases
WIDE_INT_MAX_ELTS
and thus increases wide_int structure. If we use 512 for
MAX_BITSIZE_MODE_ANY_INT then
wide_int structure would grow by 48 bytes (16 bytes if use 256 for
MAX_BITSIZE_MODE_ANY_INT).
Is it OK for such narrow usage?
Ilya
>
> Richard.
>
>> Ilya
>>
>>>
>>> Richard.
>>>
>>>> Yuri.
>>>>
>>>>
next prev parent reply other threads:[~2015-11-10 14:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 14:04 Yuri Rumyantsev
2015-05-08 9:27 ` Richard Biener
2015-05-08 18:43 ` Jeff Law
2015-05-08 19:16 ` Richard Biener
2015-05-20 14:10 ` Yuri Rumyantsev
2015-05-29 14:28 ` Yuri Rumyantsev
2015-06-09 12:15 ` Richard Biener
2015-06-18 15:41 ` Yuri Rumyantsev
2015-07-07 13:55 ` Yuri Rumyantsev
2015-07-10 5:51 ` Jeff Law
2015-07-20 15:26 ` Yuri Rumyantsev
2015-07-21 13:59 ` Richard Biener
2015-07-23 20:32 ` Jeff Law
2015-07-24 9:04 ` Yuri Rumyantsev
2015-07-24 9:24 ` Richard Biener
2015-07-24 19:26 ` Jeff Law
2015-07-27 9:04 ` Richard Biener
2015-08-06 11:07 ` Yuri Rumyantsev
2015-08-13 11:40 ` Yuri Rumyantsev
2015-08-13 11:46 ` Richard Biener
2015-11-02 15:24 ` Yuri Rumyantsev
2015-11-05 15:49 ` Yuri Rumyantsev
2015-11-06 12:56 ` Richard Biener
2015-11-06 13:29 ` Yuri Rumyantsev
2015-11-10 12:33 ` Richard Biener
2015-11-10 12:48 ` Ilya Enkovich
2015-11-10 14:46 ` Richard Biener
2015-11-10 14:56 ` Ilya Enkovich [this message]
2015-11-10 17:02 ` Mike Stump
2015-11-11 9:18 ` Richard Biener
2015-11-11 13:13 ` Yuri Rumyantsev
2015-11-12 13:59 ` Richard Biener
2015-11-19 15:20 ` Yuri Rumyantsev
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=CAMbmDYYdqVRLorQT1VcS0rJON-ugvU-bFdFRb5y_K_AJNJoYDA@mail.gmail.com \
--to=enkovich.gnu@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=izamyatin@gmail.com \
--cc=law@redhat.com \
--cc=richard.guenther@gmail.com \
--cc=ysrumyan@gmail.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).