public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kyrill Tkachov <kyrylo.tkachov@arm.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	 Jeff Law <law@redhat.com>, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH][RTL-ifcvt] Improve conditional select ops on immediates
Date: Mon, 10 Aug 2015 09:44:00 -0000	[thread overview]
Message-ID: <55C87266.5040007@arm.com> (raw)
In-Reply-To: <CAFULd4Ym6pRzTYQAC6nqAavR-ucoWBUv98PjTWOuVbHJqYzzsw@mail.gmail.com>


On 10/08/15 10:43, Uros Bizjak wrote:
> On Mon, Aug 10, 2015 at 11:36 AM, Kyrill Tkachov <kyrylo.tkachov@arm.com> wrote:
>
>>>>> I'm testing a patch that fix the testcases on x86_64 and does not
>>>>> harm codegen on aarch64. Feel free to file a PR and assign it to me.
>>>> PR67103 [1]
>>>>
>>>> [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67103
>>> Thanks,
>>> Here's the patch to move that transformation from
>>> noce_try_store_flag_constants
>>> to noce_try_cmove after the target-specific expansion has had a go.
>>>
>>> This fixes the testcases for me on x86_64.
>>> In i386.exp I only see:
>>> FAIL: gcc.target/i386/pr49781-1.c scan-assembler-not lea[lq]?[
>>> \t]\\((%|)r[a-z0-9]*
>>> FAIL: gcc.target/i386/pr61403.c scan-assembler blend
>>>
>>> which were there before my patch.
>>> Bootstrap and testing on x86_64, arm and aarch64 is successful for me.
>>>
>>> Is this ok?
>>
>> Ping.
>> Uros, does the codegen with this patch look ok to you?
> Yes, the code of previously failing testcases looks OK.
>
> You will need an approval from rtl-optimization maintainer, though.

Sure, thanks for confirming.

Kyrill

>
> Uros.
>

  reply	other threads:[~2015-08-10  9:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 12:33 Uros Bizjak
2015-08-03 13:02 ` Kyrill Tkachov
2015-08-03 13:37   ` Uros Bizjak
2015-08-03 13:43     ` Kyrill Tkachov
2015-08-03 14:12       ` Kyrill Tkachov
2015-08-03 14:15       ` Uros Bizjak
2015-08-03 15:37         ` Kyrill Tkachov
2015-08-03 15:46           ` Uros Bizjak
2015-08-03 15:53             ` Kyrill Tkachov
2015-08-03 17:20               ` Kyrill Tkachov
2015-08-03 17:37                 ` Uros Bizjak
2015-08-04  8:44                   ` Kyrill Tkachov
2015-08-10  9:36                     ` Kyrill Tkachov
2015-08-10  9:43                       ` Uros Bizjak
2015-08-10  9:44                         ` Kyrill Tkachov [this message]
2015-08-12 17:52                     ` Jeff Law
2015-08-03 14:04   ` Uros Bizjak
2015-08-03 14:37     ` H.J. Lu
2015-08-03 15:50     ` Ilya Enkovich
2015-08-03 16:29       ` Jeff Law
  -- strict thread matches above, loose matches on Subject: below --
2015-07-29 14:16 Kyrill Tkachov
2015-07-29 22:46 ` Jeff Law
2015-07-30 14:30   ` Kyrill Tkachov
2015-07-31 16:16     ` Jeff Law

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=55C87266.5040007@arm.com \
    --to=kyrylo.tkachov@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=law@redhat.com \
    --cc=ubizjak@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).