public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/31528] Inlining with -Os increases code size Date: Thu, 22 Nov 2007 22:01:00 -0000 [thread overview] Message-ID: <20071122220055.12256.qmail@sourceware.org> (raw) In-Reply-To: <bug-31528-11199@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from rguenth at gcc dot gnu dot org 2007-11-22 22:00 ------- Same results on current trunk. Early inlining is already doing it because we think putchs size (4 insns) when inlined will reduce the compilation units size by 4 insns (the out-of-line copy of putch). putchs IL before inlining looks like <bb 2>: <bb 4>: D.1182_2 ={v} *43B; D.1183_3 = (int) D.1182_2; D.1184_4 = D.1183_3 & 32; if (D.1184_4 == 0) goto <bb 4>; else goto <bb 3>; <bb 3>: ch.0_7 = (volatile unsigned char) ch_6(D); *44B ={v} ch.0_7; return; we count INDIRECT_REFs as having no cost, the only thing what counts is the BIT_AND_EXPR and the comparison. Constants and registers also have no cost. Considering the (currently) recursive structure of estimate_num_insns_1 it is non-trivial to adjust the container-like reference trees (but the INDIREC_REF ones). -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 GCC target triplet|*-*-* | Keywords| |missed-optimization Known to fail|4.1.2 |4.1.2 4.3.0 Last reconfirmed|0000-00-00 00:00:00 |2007-11-22 22:00:55 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31528
next prev parent reply other threads:[~2007-11-22 22:01 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-04-10 13:36 [Bug middle-end/31528] New: " j at uriah dot heep dot sax dot de 2007-04-10 13:38 ` [Bug middle-end/31528] " j at uriah dot heep dot sax dot de 2007-04-10 13:40 ` j at uriah dot heep dot sax dot de 2007-04-10 13:41 ` j at uriah dot heep dot sax dot de 2007-04-10 14:38 ` j at uriah dot heep dot sax dot de 2007-04-10 15:38 ` [Bug target/31528] " steven at gcc dot gnu dot org 2007-04-10 16:15 ` [Bug middle-end/31528] " j at uriah dot heep dot sax dot de 2007-04-10 20:04 ` j at uriah dot heep dot sax dot de 2007-11-22 22:01 ` rguenth at gcc dot gnu dot org [this message] 2010-09-07 11:36 ` abnikant dot singh at atmel dot com [not found] <bug-31528-4@http.gcc.gnu.org/bugzilla/> 2010-11-10 13:51 ` hubicka at gcc dot gnu.org 2010-11-11 11:00 ` j at uriah dot heep.sax.de 2011-01-11 18:40 ` hubicka 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=20071122220055.12256.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).