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/39141] overzealous unrolling (peeling) destroys code locality Date: Wed, 27 Jan 2010 20:04:00 -0000 [thread overview] Message-ID: <20100127200411.16718.qmail@sourceware.org> (raw) In-Reply-To: <bug-39141-5394@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from amylaar at gcc dot gnu dot org 2010-01-27 20:04 ------- Subject: Bug 39141 Author: amylaar Date: Wed Jan 27 20:03:57 2010 New Revision: 156301 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=156301 Log: PR tree-optimization/39141 * tree-ssa-loop-manip.c (gimple_can_duplicate_loop_to_header_edge): New function. * tree-ssa-loop-ivcanon.c (enum unroll_level): New value UL_ESTIMATE_GROWTH. (try_unroll_loop_completely): Handle UL_ESTIMATE_GROWTH. (canonicalize_loop_induction_variables): Likewise. (tree_unroll_loops_completely): Don't completely unroll loops where the outer loop/function is larger than PARAM_MAX_COMPLETELY_PEELED_OUTER_INSNS, or will/would become thus due to unrolling. * cfgloop.h (enum li_flags): New value LI_REALLY_FROM_INNERMOST. (fel_init): Handle LI_REALLY_FROM_INNERMOST. * tree-flow.h (gimple_can_duplicate_loop_to_header_edge): Declare. * params.def (PARAM_MAX_COMPLETELY_PEELED_OUTER_INSNS): New parameter. Added: branches/mpost-opt-imp-20100127/gcc/ChangeLog.mpost Modified: branches/mpost-opt-imp-20100127/gcc/cfgloop.h branches/mpost-opt-imp-20100127/gcc/params.def branches/mpost-opt-imp-20100127/gcc/tree-flow.h branches/mpost-opt-imp-20100127/gcc/tree-ssa-loop-ivcanon.c branches/mpost-opt-imp-20100127/gcc/tree-ssa-loop-manip.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39141
prev parent reply other threads:[~2010-01-27 20:04 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-09 16:18 [Bug tree-optimization/39141] New: " amylaar at gcc dot gnu dot org 2009-03-04 19:09 ` [Bug tree-optimization/39141] " amylaar at gcc dot gnu dot org 2009-03-05 0:34 ` amylaar at gcc dot gnu dot org 2010-01-27 20:04 ` amylaar at gcc dot gnu dot org [this message]
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=20100127200411.16718.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).