public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/65443] New: Don't peel last iteration from loop in transform_to_exit_first_loop Date: Mon, 16 Mar 2015 15:45:00 -0000 [thread overview] Message-ID: <bug-65443-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65443 Bug ID: 65443 Summary: Don't peel last iteration from loop in transform_to_exit_first_loop Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org tree-parloops.c ( https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/tree-parloops.c;h=fbb9eebddcf23e0c3498668e7aaa4708d302f255;hb=HEAD#l1503 ): ... TODO: the common case is that latch of the loop is empty and immediately follows the loop exit. In this case, it would be better not to copy the body of the loop, but only move the entry of the loop directly before the exit check and increase the number of iterations of the loop by one. This may need some additional preconditioning in case NIT = ~0. REDUCTION_LIST describes the reductions in LOOP. */ static void transform_to_exit_first_loop (struct loop *loop, reduction_info_table_type *reduction_list, tree nit) ...
next reply other threads:[~2015-03-16 15:45 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-16 15:45 vries at gcc dot gnu.org [this message] 2015-03-16 17:12 ` [Bug tree-optimization/65443] " vries at gcc dot gnu.org 2015-03-16 17:27 ` vries at gcc dot gnu.org 2015-03-17 19:43 ` vries at gcc dot gnu.org 2015-03-18 11:34 ` rguenth at gcc dot gnu.org 2015-03-19 23:56 ` vries at gcc dot gnu.org 2015-03-20 20:08 ` vries at gcc dot gnu.org 2015-03-20 20:10 ` vries at gcc dot gnu.org 2015-03-20 20:14 ` vries at gcc dot gnu.org 2015-03-22 12:44 ` vries at gcc dot gnu.org 2015-03-23 9:02 ` vries at gcc dot gnu.org 2015-03-26 8:50 ` vries at gcc dot gnu.org 2015-03-26 12:28 ` vries at gcc dot gnu.org 2015-03-27 14:51 ` vries at gcc dot gnu.org 2015-04-03 12:45 ` vries at gcc dot gnu.org 2015-04-16 8:53 ` vries at gcc dot gnu.org 2015-05-28 21:24 ` vries at gcc dot gnu.org 2015-06-05 15:58 ` vries at gcc dot gnu.org 2015-06-05 16:01 ` vries at gcc dot gnu.org 2015-06-08 12:01 ` vries 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-65443-4@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).