public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "changpeng dot fang at amd dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/44794] pre- and post-loops should not be unrolled. Date: Tue, 06 Jul 2010 17:59:00 -0000 [thread overview] Message-ID: <20100706175854.7719.qmail@sourceware.org> (raw) In-Reply-To: <bug-44794-18740@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from changpeng dot fang at amd dot com 2010-07-06 17:58 ------- We also need to handle the post loop of unrolling. Suppose the unroll_factor is 16, then the post-loop should have up to 15 iterations. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44794
next prev parent reply other threads:[~2010-07-06 17:59 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-02 23:54 [Bug tree-optimization/44794] New: " changpeng dot fang at amd dot com 2010-07-03 10:48 ` [Bug tree-optimization/44794] " rguenth at gcc dot gnu dot org 2010-07-06 17:59 ` changpeng dot fang at amd dot com [this message] 2010-07-06 18:36 ` changpeng dot fang at amd dot com 2010-07-15 1:50 ` changpeng dot fang at amd dot com [not found] <bug-44794-4@http.gcc.gnu.org/bugzilla/> 2023-03-09 8:06 ` rguenth at gcc dot gnu.org 2023-04-19 11:51 ` cvs-commit at gcc dot gnu.org 2023-04-19 11:53 ` rguenth at gcc dot gnu.org 2023-04-19 11:55 ` 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=20100706175854.7719.qmail@sourceware.org \ --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).