RE: Perf : put all the code in one source file only ?

RE: Perf : put all the code in one source file only ?

[Alain Meunier]

Thanks,

Why would I use flto with a single file at the first place ?

________________________________
> Date: Sat, 2 Aug 2014 14:12:31 -0400 
> Subject: RE: Perf : put all the code in one source file only ? 
> From: n8tm@aol.com 
> To: deco33@hotmail.fr; gcc-help@gcc.gnu.org 
>  
> Single file permits some auto inlining even without flto. 
>  
> Tim Prince 
>  
>  
> -------- Original message -------- 
> From: Alain Meunier <deco33@hotmail.fr> 
> Date: 
> To: gcc-help@gcc.gnu.org 
> Subject: Perf : put all the code in one source file only ? 
>  
>  
> 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, 
>  
 		 	   		  

Perf : put all the code in one source file only ?

[Alain Meunier]

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,