public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/99407] s243 benchmark of TSVC is vectorized by clang and not by gcc
Date: Fri, 05 Mar 2021 14:04:35 +0000 [thread overview]
Message-ID: <bug-99407-4-kVcAz4plzh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99407-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99407
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Here we get:
s243.c:27:18: missed: not vectorized, possible dependence between data-refs
a[i_29] and a[_9]
s243.c:26:27: missed: bad data dependence.
s243.c:26:27: note: ***** Analysis failed with vector mode V8QI
<bb 6> [local count: 1052266997]:
<bb 3> [local count: 1063004410]:
# i_29 = PHI <_9(6), 0(4)>
# ivtmp_43 = PHI <ivtmp_42(6), 31999(4)>
_1 = b[i_29];
_2 = c[i_29];
_3 = d[i_29];
_4 = _2 * _3;
_5 = _1 + _4;
a[i_29] = _5;
_6 = e[i_29];
_7 = _3 * _6;
_8 = _5 + _7;
b[i_29] = _8;
_9 = i_29 + 1;
_10 = a[_9];
_11 = _3 * _10;
_12 = _8 + _11;
a[i_29] = _12;
ivtmp_42 = ivtmp_43 - 1;
if (ivtmp_42 != 0)
goto <bb 6>; [98.99%]
else
goto <bb 5>; [1.01%]
next prev parent reply other threads:[~2021-03-05 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 14:01 [Bug middle-end/99407] New: " hubicka at gcc dot gnu.org
2021-03-05 14:04 ` hubicka at gcc dot gnu.org [this message]
2021-03-08 8:11 ` [Bug tree-optimization/99407] s243 benchmark of TSVC is vectorized by clang and not by gcc, missed DSE rguenth at gcc dot gnu.org
2022-09-22 10:52 ` cvs-commit at gcc dot gnu.org
2022-09-22 10:53 ` rguenth at gcc dot gnu.org
2022-09-22 15:56 ` pinskia at gcc dot gnu.org
2023-12-12 3:18 ` pinskia at gcc dot gnu.org
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=bug-99407-4-kVcAz4plzh@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).