public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/29946] New: inept unrolling for small iteration counts Date: Wed, 22 Nov 2006 19:47:00 -0000 [thread overview] Message-ID: <bug-29946-5394@http.gcc.gnu.org/bugzilla/> (raw) When profile based feedback indicates that a loop has a low iteration count, it will often refuse to unroll even though unrolling is still useful. Moreover, while it knows about the average loop iteration count, it lacks the concept of a prevalent iteration count. In particular, the header checksumming of the EEMBC packetflow benchmark usually has ten iterations. With gcc 3.x, unrolling was by a factor of four, which was mediocre. With the introduction of the new loop unroller in 4.0, unrolling when doing profile feedback was no longer done at all. The proper thing to do would be to unroll this loop five times. When the case of a loop that is not a multiple of the chosen unroll factor is deemed sufficiently unlikely, that case can be taken care of by generating a non-unrolled loop after the unrolled loop. The unrolled loop can use a suitably transformed unequality check for the loop start and end to verify that a sufficient number of iterations is outstanding, so that no casesi / tablejump code is needed. See also: http://gcc.gnu.org/ml/gcc-patches/2004-09/msg02373.html -- Summary: inept unrolling for small iteration counts Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: amylaar at gcc dot gnu dot org OtherBugsDependingO 29842 nThis: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29946
next reply other threads:[~2006-11-22 19:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-22 19:47 amylaar at gcc dot gnu dot org [this message] 2006-11-22 19:49 ` [Bug tree-optimization/29946] " pinskia at gcc dot gnu dot org 2006-11-22 20:10 ` amylaar at gcc dot gnu dot 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-29946-5394@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).