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/99395] s116 benchmark of TSVC is vectorized by clang and not by gcc Date: Thu, 04 Mar 2021 23:24:50 +0000 [thread overview] Message-ID: <bug-99395-4-tqRktyhMKV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99395-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99395 --- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Loop is: real_t s116 (struct args_t * func_args) { int i; int nl; static const char __func__[5] = "s116"; struct timeval * _1; int _2; float _3; float _4; float _5; int _6; float _7; float _8; float _9; int _10; float _11; float _12; float _13; int _14; float _15; float _16; float _17; int _18; float _19; float _20; float _21; struct timeval * _22; real_t _33; unsigned int ivtmp_43; unsigned int ivtmp_44; unsigned int ivtmp_45; unsigned int ivtmp_46; <bb 2> [local count: 108459]: initialise_arrays (&__func__); _1 = &func_args_29(D)->t1; gettimeofday (_1, 0B); goto <bb 5>; [100.00%] <bb 8> [local count: 1052266996]: <bb 3> [local count: 1063004409]: # i_48 = PHI <_18(8), 0(5)> # ivtmp_46 = PHI <ivtmp_45(8), 6399(5)> _2 = i_48 + 1; _3 = a[_2]; _4 = a[i_48]; _5 = _3 * _4; a[i_48] = _5; _6 = i_48 + 2; _7 = a[_6]; _8 = a[_2]; _9 = _7 * _8; a[_2] = _9; _10 = i_48 + 3; _11 = a[_10]; _12 = a[_6]; _13 = _11 * _12; a[_6] = _13; _14 = i_48 + 4; _15 = a[_14]; _16 = a[_10]; _17 = _15 * _16; a[_10] = _17; _18 = i_48 + 5; _19 = a[_18]; _20 = a[_14]; _21 = _19 * _20; a[_14] = _21; ivtmp_45 = ivtmp_46 - 1; if (ivtmp_45 != 0) goto <bb 8>; [98.99%] else goto <bb 4>; [1.01%] tsvc.c:275:18: missed: not vectorized, possible dependence between data-refs a[i_48] and a[_18] tsvc.c:274:27: missed: bad data dependence. _18 = i_48 + 5 and stride is 5...
next prev parent reply other threads:[~2021-03-04 23:24 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-04 23:01 [Bug middle-end/99395] New: " hubicka at gcc dot gnu.org 2021-03-04 23:24 ` hubicka at gcc dot gnu.org [this message] 2021-03-05 8:27 ` [Bug tree-optimization/99395] " rguenth at gcc dot gnu.org 2021-03-05 15:42 ` hubicka at gcc dot gnu.org 2022-10-18 10:28 ` rguenth at gcc dot gnu.org 2022-10-18 10:37 ` rguenth at gcc dot gnu.org 2023-10-07 9:10 ` juzhe.zhong at rivai dot ai 2023-10-09 6:30 ` rguenth at gcc dot gnu.org 2024-01-30 11:37 ` juzhe.zhong at rivai dot ai 2024-01-30 12:26 ` rguenth at gcc dot gnu.org 2024-01-31 1:32 ` juzhe.zhong at rivai dot ai 2024-01-31 3:50 ` juzhe.zhong at rivai dot ai 2024-01-31 7:00 ` juzhe.zhong at rivai dot ai 2024-01-31 7:59 ` rguenth at gcc dot gnu.org 2024-01-31 8:09 ` juzhe.zhong at rivai dot ai 2024-01-31 8:18 ` rguenther at suse dot de 2024-01-31 8:27 ` juzhe.zhong at rivai dot ai 2024-01-31 9:08 ` rguenther at suse dot de 2024-01-31 9:19 ` juzhe.zhong at rivai dot ai 2024-01-31 9:56 ` rguenther at suse dot de 2024-04-07 21:33 ` 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-99395-4-tqRktyhMKV@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: linkBe 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).