From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] tree-optimization/113552 - fix num_call accounting in simd clone vectorization
Date: Tue, 23 Jan 2024 13:01:40 +0100 [thread overview]
Message-ID: <Za+qpD0IQM2DHyJm@tucnak> (raw)
In-Reply-To: <20240123115653.47E5C136A4@imap1.dmz-prg2.suse.org>
On Tue, Jan 23, 2024 at 12:56:52PM +0100, Richard Biener wrote:
> The following avoids using exact_log2 on the number of SIMD clone calls
> to be emitted when vectorizing calls since that can easily be not
> a power of two in which case it will return -1. For different simd
> clones the number of calls will differ by a multiply with a power of two
> only so using floor_log2 is good enough here.
>
> Bootstrap and regtest running on x86_64-unknown-linux-gnu.
>
> PR tree-optimization/113552
> * tree-vect-stmts.cc (vectorizable_simd_clone_call): Use
> floor_log2 instead of exact_log2 on the number of calls.
Is there any target which supports non-power-of-two simdlen?
If not, perhaps we should add !pow2p_hwi (num_calls) to the continue;
condition a few lines earlier?
> diff --git a/gcc/tree-vect-stmts.cc b/gcc/tree-vect-stmts.cc
> index 09749ae3817..1dbe1115da4 100644
> --- a/gcc/tree-vect-stmts.cc
> +++ b/gcc/tree-vect-stmts.cc
> @@ -4071,7 +4071,7 @@ vectorizable_simd_clone_call (vec_info *vinfo, stmt_vec_info stmt_info,
> || (nargs != simd_nargs))
> continue;
> if (num_calls != 1)
> - this_badness += exact_log2 (num_calls) * 4096;
> + this_badness += floor_log2 (num_calls) * 4096;
> if (n->simdclone->inbranch)
> this_badness += 8192;
> int target_badness = targetm.simd_clone.usable (n);
> --
> 2.35.3
Jakub
next prev parent reply other threads:[~2024-01-23 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 11:56 Richard Biener
2024-01-23 12:01 ` Jakub Jelinek [this message]
2024-01-23 12:03 ` Richard Biener
2024-01-23 12:21 ` Jakub Jelinek
2024-01-23 12:40 ` Richard Biener
2024-01-23 12:43 ` Jakub Jelinek
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=Za+qpD0IQM2DHyJm@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).