From: Ian Lance Taylor <iant@google.com>
To: Suma Sharma <Suma.Sharma@kpitcummins.com>
Cc: "gcc-help\@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Increase in code size for c++ applications using GCC-4.4.1
Date: Fri, 28 Aug 2009 17:29:00 -0000 [thread overview]
Message-ID: <m3k50ovxgw.fsf@google.com> (raw)
In-Reply-To: <371569CBCFB2E745B891DBB88B2DFDDD16FB8528BD@KCINPUNHJCMS01.kpit.com> (Suma Sharma's message of "Thu\, 27 Aug 2009 19\:35\:47 +0530")
Suma Sharma <Suma.Sharma@kpitcummins.com> writes:
> While doing benchmarking of the above two toolchains (for C++
> application) it was observed that the size of the text section for
> H8-Toolchain-I had increased by approximately 66% as compared to that
> of H8-Toolchain-II.
I don't know what your test case is, but my first guess would be that
this is due to changes in the inliner. If code size is of primary
concern, you should compile with -Os. If it is only secondary, then use
-O2 and experiment with -finline-limit=NNN.
Ian
next prev parent reply other threads:[~2009-08-28 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 20:10 Suma Sharma
2009-08-28 17:29 ` Ian Lance Taylor [this message]
2009-09-01 14:56 ` Suma Sharma
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=m3k50ovxgw.fsf@google.com \
--to=iant@google.com \
--cc=Suma.Sharma@kpitcummins.com \
--cc=gcc-help@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: link
Be 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).