public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fredrik.hederstierna@securitas-direct.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/67213] When compiling for size with -Os loops can get bigger after peeling Date: Fri, 14 Aug 2015 11:06:00 -0000 [thread overview] Message-ID: <bug-67213-4-f6boyMw3ce@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67213-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67213 --- Comment #3 from Fredrik Hederstierna <fredrik.hederstierna@securitas-direct.com> --- Created attachment 36186 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36186&action=edit Dump from tree-ssa-loop-ivcanon.c In the function iter_6 it seems like it will keep cost 5 when unrolling. Maybe the weights and costs estimations could be more pessimistic when optimizing for size? I think functions tree_estimate_loop_size() and estimated_unrolled_size() uses a rough number guess of 1/3, perhaps it could be more pessimistic eg. for -Os?
prev parent reply other threads:[~2015-08-14 11:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-14 9:21 [Bug tree-optimization/67213] New: " fredrik.hederstierna@securitas-direct.com 2015-08-14 9:28 ` [Bug tree-optimization/67213] " fredrik.hederstierna@securitas-direct.com 2015-08-14 10:01 ` rguenth at gcc dot gnu.org 2015-08-14 11:06 ` fredrik.hederstierna@securitas-direct.com [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=bug-67213-4-f6boyMw3ce@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).