public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Bernd Schmidt <bschmidt@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, richard.sandiford@arm.com
Subject: Re: Use combined_fn in tree-vrp.c
Date: Tue, 10 Nov 2015 10:04:00 -0000	[thread overview]
Message-ID: <CAFiYyc18vytW_NDBfe3U+O9_h2BV1Bh9L4Jmhmde=7wK5Ko_mA@mail.gmail.com> (raw)
In-Reply-To: <564135C7.6030405@redhat.com>

On Tue, Nov 10, 2015 at 1:09 AM, Bernd Schmidt <bschmidt@redhat.com> wrote:
> On 11/07/2015 01:46 PM, Richard Sandiford wrote:
>>
>> @@ -3814,8 +3817,8 @@ extract_range_basic (value_range *vr, gimple *stmt)
>>           break;
>>           /* Both __builtin_ffs* and __builtin_popcount return
>>              [0, prec].  */
>> -       CASE_INT_FN (BUILT_IN_FFS):
>> -       CASE_INT_FN (BUILT_IN_POPCOUNT):
>> +       CASE_CFN_FFS:
>> +       CASE_CFN_POPCOUNT:
>>           arg = gimple_call_arg (stmt, 0);
>>           prec = TYPE_PRECISION (TREE_TYPE (arg));
>>           mini = 0;
>
>
> So let me see if I understood this. From what we discussed the purpose of
> these new internal functions is that they can have vector types. If so,
> isn't this code (here and elsewhere) which expects integers potentially
> going to be confused?

We indeed need to add additional checks to most users of CASE_CFN_* to cover
the bigger freedom that exists with respect to types.

Richard, please audit all the cases you change for that.

Thanks,
Richard.

>
>
> Bernd

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 12:46 Richard Sandiford
2015-11-09 22:37 ` Jeff Law
2015-11-10  0:09 ` Bernd Schmidt
2015-11-10 10:04   ` Richard Biener [this message]
2015-11-13 11:27     ` Richard Sandiford
2015-11-16 13:50       ` Richard Biener

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='CAFiYyc18vytW_NDBfe3U+O9_h2BV1Bh9L4Jmhmde=7wK5Ko_mA@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=bschmidt@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.sandiford@arm.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).