public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101910] [12 Regression] tsvc regressions for -O2 -ftree-loop-vectorize at zen hardware Date: Tue, 08 Mar 2022 14:43:15 +0000 [thread overview] Message-ID: <bug-101910-4-uyP8JtIeFi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101910-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101910 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org, | |rguenth at gcc dot gnu.org --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- https://lnt.opensuse.org/db_default/v4/CPP/latest_runs_report shows regressions for s422, in the GCC testsuite copy we do not vectorize this with -O2 since it requires versioning for aliasing. /home/rguenther/src/gcc3/gcc/testsuite/gcc.dg/vect/tsvc/vect-tsvc-s422.c:21:34: missed: versioning for alias required: can't determine dependence between flat_2d_array[_1] and *_7 consider run-time aliasing test between flat_2d_array[_1] and *_7. That's because the code does xx = flat_2d_array + 4; for (int nl = 0; nl < 8*iterations; nl++) { for (int i = 0; i < LEN_1D; i++) { xx[i] = flat_2d_array[i + 8] + a[i]; } dummy(a, b, c, d, e, aa, bb, cc, 0.); } but 'dummy' is not known to not clobber 'xx'. While xx is declared __restrict that dummy call still gets in the way. So I wonder what variant LNT exactly benchmarks.
next prev parent reply other threads:[~2022-03-08 14:43 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-14 14:33 [Bug middle-end/101910] New: " hubicka at gcc dot gnu.org 2021-08-25 7:50 ` [Bug tree-optimization/101910] " crazylht at gmail dot com 2022-03-07 21:29 ` [Bug tree-optimization/101910] [12 Regression] " pinskia at gcc dot gnu.org 2022-03-08 14:43 ` rguenth at gcc dot gnu.org [this message] 2022-03-08 14:53 ` marxin at gcc dot gnu.org 2022-03-08 14:54 ` marxin at gcc dot gnu.org 2022-03-08 15:06 ` rguenth 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-101910-4-uyP8JtIeFi@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).