public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Ming Cheng <chengm349@hotmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Fw: binary size
Date: Wed, 5 Jan 2022 08:13:55 +0000	[thread overview]
Message-ID: <CAH6eHdRC2Ef8qFM=JDT3uwqGesfo8+7vTst5y4rpY62dYMG+Kw@mail.gmail.com> (raw)
In-Reply-To: <SI2PR03MB52423230ED4334D6517FA980FB4B9@SI2PR03MB5242.apcprd03.prod.outlook.com>

On Wed, 5 Jan 2022, 08:11 Ming Cheng via Gcc-help, <gcc-help@gcc.gnu.org>
wrote:

>
>
> Hi Jonathan,
>
> Thanks for this nice advice. I'd like to learn more about cmd size. Among
> text/data/bss sections, which section(s) has the most impact to the perf?
> You are right that people should do actual test. But for the same code, in
> theory, larger size's perf should be always <= smaller size's .
>


Not necessarily. Function inlining can increase size but also increase
performance. You need to measure.

  reply	other threads:[~2022-01-05  8:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MW3PR18MB3675DED196E7FA7E19455E15804A9@MW3PR18MB3675.namprd18.prod.outlook.com>
2022-01-04  2:12 ` Ming Cheng
2022-01-04  7:53   ` Jonathan Wakely
2022-01-04 11:42     ` Ming Cheng
2022-01-04 11:46       ` Ming Cheng
2022-01-04 12:12       ` Jonathan Wakely
     [not found]         ` <SI2PR03MB5242FA109CAEDEBF0896B2AAFB4B9@SI2PR03MB5242.apcprd03.prod.outlook.com>
2022-01-05  8:10           ` Ming Cheng
2022-01-05  8:13             ` Jonathan Wakely [this message]
2022-01-05  9:15               ` Ming Cheng

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='CAH6eHdRC2Ef8qFM=JDT3uwqGesfo8+7vTst5y4rpY62dYMG+Kw@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=chengm349@hotmail.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).