public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alain Meunier <deco33@hotmail.fr>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Perf : put all the code in one source file only ?
Date: Sat, 02 Aug 2014 17:23:00 -0000	[thread overview]
Message-ID: <DUB121-W72A023E94B6A74025C6CFB7E40@phx.gbl> (raw)
In-Reply-To: <DUB121-W1390C3EF77DDFFEF6F7D09B7E40@phx.gbl>

Hello,

My question is purely theorical : what are the eventual disadvantages of putting a lot of functions in the same main.c file instead of spanning them into multiple static libraries ?

How will gcc sort this out ?

This question is neither related to maintainability, nor readability, nor executable size, nor ram usage.

Just performance.

Will the code units play a role or something ? Or whatever I don't think of ?

Will the perf will be the same ?

Thanks,
 		 	   		   		 	   		  

       reply	other threads:[~2014-08-02 17:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DUB121-W1390C3EF77DDFFEF6F7D09B7E40@phx.gbl>
2014-08-02 17:23 ` Alain Meunier [this message]
     [not found] <bn88y4h037nanottoun7i38u.1407003151444@email.android.com>
2014-08-03  7:38 ` Alain Meunier

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=DUB121-W72A023E94B6A74025C6CFB7E40@phx.gbl \
    --to=deco33@hotmail.fr \
    --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).