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 tree-optimization/99414] s235, s2233 and s233 benchmarks of TSVC is vectorized better by icc than gcc (loop interchange) Date: Wed, 17 Mar 2021 18:32:32 +0000 [thread overview] Message-ID: <bug-99414-4-sxmlHmy9wN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99414-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99414 Jan Hubicka <hubicka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|s235 and s233 benchmarks of |s235, s2233 and s233 |TSVC is vectorized better |benchmarks of TSVC is |by icc than gcc (loop |vectorized better by icc |interchange) |than gcc (loop interchange) --- Comment #3 from Jan Hubicka <hubicka at gcc dot gnu.org> --- this one is 7s with gcc and 0.4s with icc. typedef float real_t; #define iterations 100000 #define LEN_1D 32000 #define LEN_2D 256 // array definitions real_t aa[LEN_2D][LEN_2D],bb[LEN_2D][LEN_2D],cc[LEN_2D][LEN_2D],tt[LEN_2D][LEN_2D]; int main(struct args_t * func_args) { // loop interchange // interchanging with one of two inner loops for (int nl = 0; nl < 100*(iterations/LEN_2D); nl++) { for (int i = 1; i < LEN_2D; i++) { for (int j = 1; j < LEN_2D; j++) { aa[j][i] = aa[j-1][i] + cc[j][i]; } for (int j = 1; j < LEN_2D; j++) { bb[i][j] = bb[i-1][j] + cc[i][j]; } } dummy(); } return aa[0][0]; }
next prev parent reply other threads:[~2021-03-17 18:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-05 15:40 [Bug middle-end/99414] New: s235 benchmark " hubicka at gcc dot gnu.org 2021-03-08 8:38 ` [Bug tree-optimization/99414] " rguenth at gcc dot gnu.org 2021-03-17 18:30 ` [Bug tree-optimization/99414] s235 and s233 benchmarks " hubicka at gcc dot gnu.org 2021-03-17 18:32 ` hubicka at gcc dot gnu.org [this message] 2021-03-17 18:42 ` [Bug tree-optimization/99414] s235, s2233, s275 " hubicka at gcc dot gnu.org 2021-03-17 18:44 ` [Bug tree-optimization/99414] s235, s2233, s275, s2275 " hubicka at gcc dot gnu.org 2021-03-18 8:26 ` 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-99414-4-sxmlHmy9wN@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).