From: Hanke Zhang <hkzhang455@gmail.com>
To: gcc@gcc.gnu.org
Subject: the elimination of if blocks in GCC during if-conversion and vectorization
Date: Thu, 12 Oct 2023 20:16:45 +0800 [thread overview]
Message-ID: <CAM_DAs-TfFKVd8AWrcx-+2OMfM03i1-ATFbnF5mhT37SDFi_bw@mail.gmail.com> (raw)
Hi, I'm recently working on vectorization of GCC. I'm stuck in a small
problem and would like to ask for advice.
For example, for the following code:
int main() {
int size = 1000;
int *foo = malloc(sizeof(int) * size);
int c1 = rand(), t1 = rand();
for (int i = 0; i < size; i++) {
if (foo[i] & c1) {
foo[i] = t1;
}
}
// prevents the loop above from being optimized
for (int i = 0; i < size; i++) {
printf("%d", foo[i]);
}
}
First of all, the if statement block in the loop will be converted to
a MASK_STORE through if-conversion optimization. But after
tree-vector, it will still become a branched form. The part of the
final disassembly structure probably looks like below(Using IDA to do
this), and you can see that there is still such a branch 'if ( !_ZF )'
in it, which will lead to low efficiency.
do
{
while ( 1 )
{
__asm
{
vpand ymm0, ymm2, ymmword ptr [rax]
vpcmpeqd ymm0, ymm0, ymm1
vpcmpeqd ymm0, ymm0, ymm1
vptest ymm0, ymm0
}
if ( !_ZF )
break;
_RAX += 8;
if ( _RAX == v9 )
goto LABEL_5;
}
__asm { vpmaskmovd ymmword ptr [rax], ymm0, ymm3 }
_RAX += 8;
}
while ( _RAX != v9 );
Why can't we just replace the vptest and if statement with some other
instructions like vpblendvb so that it can be faster? Or is there a
good way to do that?
Thanks
Hanke Zhang
next reply other threads:[~2023-10-12 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 12:16 Hanke Zhang [this message]
2023-10-17 9:23 ` Richard Biener
2023-10-17 11:54 ` Hanke Zhang
2023-10-17 11:57 ` Richard Biener
2023-10-17 12:39 ` Hanke Zhang
2023-10-19 11:57 ` Richard Biener
2023-10-23 10:50 ` Hanke Zhang
2023-10-23 12:29 ` Richard Biener
2023-10-23 12:56 ` Hanke Zhang
2023-10-26 9:18 ` 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=CAM_DAs-TfFKVd8AWrcx-+2OMfM03i1-ATFbnF5mhT37SDFi_bw@mail.gmail.com \
--to=hkzhang455@gmail.com \
--cc=gcc@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).