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: [PATCH, PR68062] Fix uniform vector operation lowering
Date: Fri, 23 Oct 2015 22:34:00 -0000	[thread overview]
Message-ID: <CAMbmDYbV67KzJSOZ=pZVdn8T_ii7ZyFXJybybQn6E4U3BfxcgQ@mail.gmail.com> (raw)
In-Reply-To: <562AA762.2030202@redhat.com>

2015-10-24 0:32 GMT+03:00 Jeff Law <law@redhat.com>:
> On 10/23/2015 09:26 AM, Ilya Enkovich wrote:
>>
>> Hi,
>>
>> This patch checks optab exists before using it vector vector statement
>> lowering.  It fixes compilation of test from PR68062 with -funsigned-char
>> option added (doesn't fix original testcase).  Bootstrapped for
>> x86_64-unknown-linux-gnu.  OK for trunk if no regressions?
>>
>> Thanks,
>> Ilya
>> --
>> gcc/
>>
>> 2015-10-23  Ilya Enkovich  <enkovich.gnu@gmail.com>
>>
>>         * tree-vect-generic.c (expand_vector_operations_1): Check
>>         optab exists before use it.
>>
>> gcc/testsuite/
>>
>> 2015-10-23  Ilya Enkovich  <enkovich.gnu@gmail.com>
>>
>>         * g++.dg/pr68062.C: New test.
>
> OK.
>
> Just curious, what was the tree code for which we couldn't find a suitable
> optab?

Those are various comparison codes.

Ilya

>
> jeff
>

  reply	other threads:[~2015-10-23 22:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 15:32 Ilya Enkovich
2015-10-23 22:23 ` Jeff Law
2015-10-23 22:34   ` Ilya Enkovich [this message]
2015-10-26  9:11     ` Richard Biener
2015-10-26  9:36       ` Ilya Enkovich
2015-10-26  9:56         ` Richard Biener
2015-10-26 10:17           ` Ilya Enkovich

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='CAMbmDYbV67KzJSOZ=pZVdn8T_ii7ZyFXJybybQn6E4U3BfxcgQ@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).