public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ilya Enkovich <enkovich.gnu@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Boolean Vector, patch 3/5] Use boolean vector in C/C++ FE
Date: Wed, 21 Oct 2015 11:24:00 -0000	[thread overview]
Message-ID: <CAMbmDYZ0Sw0GDsuqaP3GGD-Ek-3x1wRxMdErvxaxq496UxxyUw@mail.gmail.com> (raw)
In-Reply-To: <5626B356.7040007@redhat.com>

2015-10-21 0:34 GMT+03:00 Jeff Law <law@redhat.com>:
> On 10/13/2015 09:59 AM, Ilya Enkovich wrote:
>>>>
>>>>
>>>> Looking into that I got an impression vector modes are used by C/C++
>>>> vector extensions only.  And I think regression testing would reveal
>>>> some
>>>> failures otherwise.
>>>
>>>
>>> Maybe this stuff hasn't bled into the Fortran front-end, but the gfortran
>>> front-end certainly has OpenMP support which presumably has vector
>>> extensions.
>>
>>
>> OpenMP extension doesn't produce any vector code in front-end. Code
>> will be produced by vectorizer anyway.
>>
>>>
>>> The fact that nothing's failing in the testsuite is encouraging, but it'd
>>> be
>>> worth spending a few minutes taking a look to see if there's something
>>> that
>>> might need updating.
>>
>>
>> I also grepped for VEC_COND_EXPR and it never occurs in front-ends
>> other than C/C++.
>
> Perfect.  Thanks.
>
> Was that the last question on the boolean vector patches?  If so, then I
> think they're OK for the trunk.
>
> jeff
>

I think there are no unanswered question. So I'll rebase it on the
latest trunk, test and commit.

Thanks,
Ilya

      reply	other threads:[~2015-10-21 11:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 14:05 Ilya Enkovich
2015-10-09 20:51 ` Jeff Law
2015-10-13 14:15   ` Ilya Enkovich
2015-10-13 15:42     ` Jeff Law
2015-10-13 15:59       ` Ilya Enkovich
2015-10-20 21:36         ` Jeff Law
2015-10-21 11:24           ` Ilya Enkovich [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=CAMbmDYZ0Sw0GDsuqaP3GGD-Ek-3x1wRxMdErvxaxq496UxxyUw@mail.gmail.com \
    --to=enkovich.gnu@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.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).