public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wbrana at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/61274] New: excessive code size with large-unit-insns Date: Wed, 21 May 2014 15:27:00 -0000 [thread overview] Message-ID: <bug-61274-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61274 Bug ID: 61274 Summary: excessive code size with large-unit-insns Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver Assignee: unassigned at gcc dot gnu.org Reporter: wbrana at gmail dot com according to docs inline-unit-growth limit is effective only when unit size is above large-unit-insns, which means if application consists of many small units with many inlineable functions, application size can be excessive if inline-unit-growth wasn't applied there should be some limit also for small units below large-unit-insns or large-unit-insns should be set to lower value e.g. 1000 instead of 10,000 or large-unit-insns should be removed, which means inline-unit-growth is always applied
next reply other threads:[~2014-05-21 15:27 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-21 15:27 wbrana at gmail dot com [this message] 2014-05-22 8:29 ` [Bug driver/61274] " rguenth at gcc dot gnu.org 2014-08-12 18:14 ` wbrana at gmail dot com
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-61274-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).