public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Michael Collison <collison@rivosinc.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v2] vect: Check that vector factor is a compile-time constant
Date: Thu, 9 Mar 2023 09:55:42 +0100	[thread overview]
Message-ID: <CAFiYyc0QKECzVG1cKUedLVQMoeOa6+ERcT6Qbk6PpSu5jqFoEQ@mail.gmail.com> (raw)
In-Reply-To: <20230309075710.2236986-1-collison@rivosinc.com>

On Thu, Mar 9, 2023 at 8:57 AM Michael Collison <collison@rivosinc.com> wrote:

OK.

Thanks,
Richard.

> 2023-03-05  Michael Collison  <collison@rivosinc.com>
>
>         * tree-vect-loop-manip.cc (vect_do_peeling): Use
>         result of constant_lower_bound instead of vf in case
>         vf is not a compile time constant.
> ---
>  gcc/tree-vect-loop-manip.cc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/tree-vect-loop-manip.cc b/gcc/tree-vect-loop-manip.cc
> index d88edafa018..f60fa50e8f4 100644
> --- a/gcc/tree-vect-loop-manip.cc
> +++ b/gcc/tree-vect-loop-manip.cc
> @@ -2921,7 +2921,7 @@ vect_do_peeling (loop_vec_info loop_vinfo, tree niters, tree nitersm1,
>        if (new_var_p)
>         {
>           value_range vr (type,
> -                         wi::to_wide (build_int_cst (type, vf)),
> +                         wi::to_wide (build_int_cst (type, lowest_vf)),
>                           wi::to_wide (TYPE_MAX_VALUE (type)));
>           set_range_info (niters, vr);
>         }
> --
> 2.34.1
>

      reply	other threads:[~2023-03-09  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09  7:57 Michael Collison
2023-03-09  8:55 ` Richard Biener [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=CAFiYyc0QKECzVG1cKUedLVQMoeOa6+ERcT6Qbk6PpSu5jqFoEQ@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=collison@rivosinc.com \
    --cc=gcc-patches@gcc.gnu.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).