public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jiu Fu Guo <guojiufu@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/guojiufu/heads/guojiufu-branch] Daily bump. Date: Wed, 8 Jul 2020 09:08:35 +0000 (GMT) [thread overview] Message-ID: <20200708090835.B608F3861019@sourceware.org> (raw) The branch 'guojiufu/heads/guojiufu-branch' was updated to point to: 8e3b453e087... Daily bump. It previously pointed to: 85a0fd39ef8... rs6000: Refine RTL unroll adjust hook for small loops Diff: !!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST): ------------------------------------------------------------------- 85a0fd3... rs6000: Refine RTL unroll adjust hook for small loops a352793... rs6000: Refine RTL unroll adjust hook commit 85a0fd39ef8df6b76df70110d096f22cfa8456c4 Author: guojiufu <guojiufu@linux.ibm.com> Date: Wed Jul 8 16:49:40 2020 +0800 rs6000: Refine RTL unroll adjust hook for small loops commit a3527937da17089b1bb95097726285fbdfff4b17 Author: guojiufu <guojiufu@linux.ibm.com> Date: Fri Jun 19 09:24:19 2020 +0800 rs6000: Refine RTL unroll adjust hook For very small loops (< 6 insns), it would be fine to unroll 4 times to use cache line better. Like below loops: `while (i) a[--i] = NULL; while (p < e) *d++ = *p++;` And for very complex loops which may cause negative impact: branch-miss or cache-miss. Like below loop: there are calls, early exits and branches in loop. ``` for (int i = 0; i < n; i++) { int e = a[I]; .... if (function_call(e)) break; .... } ``` This patch enhance RTL unroll for small loops and prevent to unroll complex loops. gcc/ChangeLog 2020-07-03 Jiufu Guo <guojiufu@linux.ibm.com> * config/rs6000/rs6000.c (rs6000_loop_unroll_adjust): Refine hook. (rs6000_complex_loop_p): New function. (num_loop_calls): New function.
next reply other threads:[~2020-07-08 9:08 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-08 9:08 Jiu Fu Guo [this message] -- strict thread matches above, loose matches on Subject: below -- 2021-05-31 6:00 Jiu Fu Guo 2020-05-27 2:23 Jiu Fu Guo
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=20200708090835.B608F3861019@sourceware.org \ --to=guojiufu@gcc.gnu.org \ --cc=gcc-cvs@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).