From: "Bin.Cheng" <amker.cheng@gmail.com>
To: kugan <kugan.vivekanandarajah@linaro.org>
Cc: Jan Hubicka <hubicka@ucw.cz>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC] Handle unary pass-through jump functions for ipa-vrp
Date: Fri, 11 Nov 2016 15:46:00 -0000 [thread overview]
Message-ID: <CAHFci28hbu62oV759dnr2ZAbdwHntPncfcCJ5HuVg-1oyddXRQ@mail.gmail.com> (raw)
In-Reply-To: <052d4b8d-3a67-b2b6-c90a-d4427b0cf5be@linaro.org>
On Tue, Nov 8, 2016 at 10:13 AM, kugan
<kugan.vivekanandarajah@linaro.org> wrote:
> Hi,
>
>
>
> On 04/11/16 04:36, Martin Jambor wrote:
>>
>> Hi,
>>
>> On Fri, Oct 28, 2016 at 02:03:47PM +1100, kugan wrote:
>>>
>>>
>>> ...snip...
>>>
>>> I have also separated the constant parameter conversion out and posted as
>>> https://gcc.gnu.org/ml/gcc-patches/2016-10/msg02309.html. This is now
>>> handling just unary pass-through jump functions.
>>>
>>> Bootstrapped and regression tested on x86_64-linux-gnu with no new
>>> regressions.
>>>
>>> Is this OK for trunk?
>>>
>>> Thanks,
>>> Kugan
>>>
>>> gcc/testsuite/ChangeLog:
>>>
>>> 2016-10-28 Kugan Vivekanandarajah <kuganv@linaro.org>
>>>
>>> * gcc.dg/ipa/vrp7.c: New test.
>>>
>>>
>>> gcc/ChangeLog:
>>>
>>> 2016-10-28 Kugan Vivekanandarajah <kuganv@linaro.org>
>>>
>>> * ipa-cp.c (ipa_get_jf_pass_through_result): Handle unary
>>> expressions.
>>> (propagate_vr_accross_jump_function): Likewise.
>>> * ipa-prop.c (ipa_set_jf_unary_pass_through): New.
>>> (load_from_param_1): New.
>>> (load_from_unmodified_param): Factor common part into
>>> load_from_param_1.
>>> (load_from_param): New.
>>> (compute_complex_assign_jump_func): Handle unary expressions.
>>> (ipa_write_jump_function): Likewise.
>>> (ipa_read_jump_function): Likewise.
>>>
>>>
>>>> Patch is OK with changes Martin suggested.
>>>>
>>>> Honza
>>>>
>>
>>> From b7d9b413951ba20d156a7801640cc7d7bc57c062 Mon Sep 17 00:00:00 2001
>>> From: Kugan Vivekanandarajah <kugan.vivekanandarajah@linaro.org>
>>> Date: Fri, 28 Oct 2016 10:16:38 +1100
>>> Subject: [PATCH 2/2] add unary jump function
>>>
>>> ---
>>> gcc/ipa-cp.c | 39 +++++++++++++++---
>>> gcc/ipa-prop.c | 89
>>> +++++++++++++++++++++++++++++++++++------
>>> gcc/testsuite/gcc.dg/ipa/vrp7.c | 32 +++++++++++++++
>>> 3 files changed, 142 insertions(+), 18 deletions(-)
>>> create mode 100644 gcc/testsuite/gcc.dg/ipa/vrp7.c
>>>
>>> diff --git a/gcc/ipa-cp.c b/gcc/ipa-cp.c
>>> index 9f28557..8fc95dd 100644
>>> --- a/gcc/ipa-cp.c
>>> +++ b/gcc/ipa-cp.c
>>> @@ -1225,13 +1225,21 @@ ipa_get_jf_pass_through_result (struct
>>> ipa_jump_func *jfunc, tree input)
>>> return NULL_TREE;
>>>
>>> if (TREE_CODE_CLASS (ipa_get_jf_pass_through_operation (jfunc))
>>> - == tcc_comparison)
>>> - restype = boolean_type_node;
>>> + == tcc_unary)
>>> + {
>>> + res = fold_unary (ipa_get_jf_pass_through_operation (jfunc),
>>> + TREE_TYPE (input), input);
>>> + }
>>
>>
>> Please do not put curly braces around a single statement. Apart from
>> that, no objection from me.
>
>
> Thanks Martin, I will fix this.
>
> Honza, is this OK for you with the above fix?
>
> Thanks,
> Kugan
>>
>>
>> Thanks,
>>
>> Martin
>>
>
Hi,
This new test fails on AArch64. I created PR78316 for tracking.
Thanks,
bin
prev parent reply other threads:[~2016-11-11 15:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 23:18 kugan
2016-10-27 12:11 ` Martin Jambor
2016-10-28 2:58 ` [ipa-vrp] ice in set_value_range kugan
2016-11-03 16:25 ` Martin Jambor
2016-11-08 10:11 ` kugan
2016-11-08 15:17 ` Jan Hubicka
2016-11-09 6:02 ` Andrew Pinski
2016-11-09 8:02 ` kugan
2016-11-10 6:14 ` Andrew Pinski
2016-11-10 6:18 ` kugan
2016-11-10 8:12 ` Andreas Schwab
2016-10-27 14:59 ` [RFC] Handle unary pass-through jump functions for ipa-vrp Jan Hubicka
2016-10-28 3:04 ` kugan
2016-11-03 17:36 ` Martin Jambor
2016-11-08 10:13 ` kugan
2016-11-08 15:17 ` Jan Hubicka
2016-11-13 8:20 ` kugan
2016-11-13 11:50 ` Jan Hubicka
2016-11-11 15:46 ` Bin.Cheng [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=CAHFci28hbu62oV759dnr2ZAbdwHntPncfcCJ5HuVg-1oyddXRQ@mail.gmail.com \
--to=amker.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=kugan.vivekanandarajah@linaro.org \
/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).