From: Kugan <kugan.vivekanandarajah@linaro.org>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 2/2] Enable elimination of zext/sext
Date: Sun, 03 Aug 2014 23:56:00 -0000 [thread overview]
Message-ID: <53DECC0F.2020505@linaro.org> (raw)
In-Reply-To: <53DBBA6B.3070507@linaro.org>
On 02/08/14 02:03, Kugan wrote:
>>>> if (rhs_uns)
>>>> return wi::ge_p (min, 0); // if min >= 0 then range contains positive values
>>>> else
>>>> return wi::le_p (max, wi::max_value (TYPE_PRECISION (TREE_TYPE
>>>> (ssa)), SIGNED); // if max <= signed-max-of-type then range doesn't
>>>> need sign-extension
>>>
>>> I think we will have to check that ssa has necessary sign/zero extension
>>> when assigned to lhs_type. If PROMOTE_MODE tells us that ssa's type will
>>> be interpreted differently, the value range of ssa also will have
>>> corresponding range. In this cases, shouldnât we have to check for
>>> upper and lower limit for both min and max?
>>
>> Hmm? That's exactly what the check is testing... we know that
>> min <= max thus if min >= 0 then max >= 0.
>>
>> zero_extension will never do anything on [0, INF]
>>
>> If max < MAX-SIGNED then sign-extension will not do anything. Ok,
>> sign-extension will do sth for negative values still. So rather
>>
>> if (rhs_uns)
>> return wi::geu_p (min, 0);
>> else
>> return wi::ges_p (min, 0) && wi::les_p (max, wi::max_value
>> (TYPE_PRECISION (TREE_TYPE (ssa)), SIGNED));
>>
>> ?
Looking at your comments again, I think we have to consider three things
here.
To be able assign to LHS (of lhs_uns and lhs_mode) without conversion of
RHS (tree SSA)
* If we ignore the mode changes (i.e. LHS_mode can be different in terms
of precision) and ignore PROMOTE_MODE and consider only the sign of LHS
and RHS
if (lhs_uns)
return wi::ge_p (min, 0, rhs_signop); // if min >= 0 then range
contains positive values
else
if (rhs_uns)
// if max <= signed-max-of-type then range doesn't need sign-extension
return wi::le_p (max, wi::max_value (TYPE_PRECISION (TREE_TYPE
(ssa)), SIGNED);
else
return true;
* However, if we consider the PROMOTE_MODE might change the RHS sign
if (lhs_uns)
{
return wi::ge_p (min, 0, rhs_signop);
}
else
{
signed_max = wide_int::from (TYPE_MAX_VALUE (lhs_type),
TYPE_PRECISION (TREE_TYPE (ssa)), rhs_signop);
if (rhs_uns)
/* If PROMOTE_MODE changed an RHS signed to unsigned and
SSA contains negative value range, we still have to do sign-extend. */
return wi::ge_p (min, 0, TYPE_SIGN (TREE_TYPE (ssa)))
&& wi::le_p (max, signed_max, rhs_signop);
else
/* If PROMOTE_MODE changed an RHS unsigned to signed and SSA contains value
range more than signed-max-of-type, we still have to do sign-extend. */
return wi::le_p (max, signed_max, TYPE_SIGN (TREE_TYPE (ssa)));
}
* If we also consider that LHS mode and RHS mode precision can be different
if (lhs_uns)
{
unsigned_max = wide_int::from (TYPE_MAX_VALUE (lhs_type),
TYPE_PRECISION (TREE_TYPE (ssa)), rhs_signop);
/* If min >= 0 then range contains positive values and doesnt need
zero-extension. If max <= unsigned-max-of-type, then value fits type. */
return wi::ge_p (min, 0, rhs_signop)
&& wi::le_p (max, unsigned_max, rhs_signop);
}
else
{
signed_max = wide_int::from (TYPE_MAX_VALUE (lhs_type),
TYPE_PRECISION (TREE_TYPE (ssa)), rhs_signop);
signed_min = wide_int::from (TYPE_MIN_VALUE (lhs_type),
TYPE_PRECISION (TREE_TYPE (ssa)), rhs_signop);
if (rhs_uns)
/* If PROMOTE_MODE changed an RHS signed to unsigned and
SSA contains negative value range, we still have to do sign-extend. */
return wi::ge_p (min, 0, TYPE_SIGN (TREE_TYPE (ssa)))
&& wi::le_p (max, signed_max, rhs_signop);
else
/* If PROMOTE_MODE changed an RHS unsigned to signed and SSA contains value
range more than signed-max-of-type, we still have to do sign-extend. */
return wi::le_p (max, signed_max, TYPE_SIGN (TREE_TYPE (ssa)))
&& wi::ge_p (min, signed_min, rhs_signop);
}
}
Since we can have PROMOTE_MODE changing the sign and LHS mode and RHS
mode precision can be different, the check should be the third one. Does
that make sense or am I still missing it?
Thanks again for your time,
Kugan
next prev parent reply other threads:[~2014-08-03 23:56 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 11:48 [PATCH 0/2] Zext/sext elimination using value range Kugan
2014-06-24 11:51 ` [PATCH 1/2] Enable setting sign and unsigned promoted mode (SPR_SIGNED_AND_UNSIGNED) Kugan
2014-06-24 12:18 ` Jakub Jelinek
2014-06-25 7:21 ` Kugan
2014-06-25 7:50 ` Jakub Jelinek
2014-06-26 1:06 ` Kugan
2014-06-26 2:48 ` Kugan
2014-06-26 5:50 ` Jakub Jelinek
2014-06-26 9:41 ` Kugan
2014-06-26 10:12 ` Jakub Jelinek
2014-06-26 10:42 ` Jakub Jelinek
2014-07-01 8:21 ` Kugan
2014-07-07 6:52 ` Kugan
2014-07-07 8:06 ` Jakub Jelinek
2014-06-26 10:25 ` Andreas Schwab
2014-07-01 8:28 ` Kugan
2014-06-24 11:53 ` [PATCH 2/2] Enable elimination of zext/sext Kugan
2014-06-24 12:21 ` Jakub Jelinek
2014-06-25 8:15 ` Kugan
2014-06-25 8:36 ` Jakub Jelinek
2014-07-07 6:55 ` Kugan
2014-07-10 12:15 ` Richard Biener
2014-07-11 11:52 ` Kugan
2014-07-11 12:47 ` Richard Biener
2014-07-14 2:58 ` Kugan
2014-07-14 20:11 ` Bernhard Reutner-Fischer
2014-07-23 14:22 ` Richard Biener
2014-08-01 4:51 ` Kugan
2014-08-01 11:16 ` Richard Biener
2014-08-01 16:04 ` Kugan
2014-08-03 23:56 ` Kugan [this message]
2014-08-05 14:18 ` Richard Biener
2014-08-05 14:21 ` Jakub Jelinek
2014-08-06 12:09 ` Richard Biener
2014-08-06 13:22 ` Kugan
2014-08-06 13:29 ` Richard Biener
2014-08-07 5:25 ` Kugan
2014-08-07 8:09 ` Richard Biener
2014-08-27 10:01 Uros Bizjak
2014-08-27 10:07 ` Richard Biener
2014-08-27 10:32 ` Uros Bizjak
2014-08-27 10:32 ` Richard Biener
2014-09-01 8:48 ` Jakub Jelinek
2014-09-01 8:54 ` Uros Bizjak
2014-08-28 7:50 ` Kugan
2014-08-28 8:57 ` Richard Biener
2014-09-04 3:41 ` Kugan
2014-09-04 13:00 ` Richard Biener
2014-09-05 1:33 ` Kugan
2014-09-05 9:51 ` Richard Biener
2014-09-07 9:51 ` Kugan
2014-09-08 9:48 ` Richard Biener
2014-09-09 10:06 ` Kugan
2014-09-09 10:28 ` Richard Biener
2014-08-27 13:02 ` Kugan
2014-08-28 3:46 ` Kugan
2014-08-28 6:44 ` Marc Glisse
2014-08-28 7:29 ` Kugan
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=53DECC0F.2020505@linaro.org \
--to=kugan.vivekanandarajah@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=richard.guenther@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).