About output size

Kempelen · 11-24-2009, 06:35 AM

Hi,

I use lots of functions to debug and for intermediate steps. When compiling, if I don't call a function, is it generated inside the output executable?

zacs7 · 11-24-2009, 07:43 AM

Quote:

Originally Posted by Kempelen

Hi,

I use lots of functions to debug and for intermediate steps. When compiling, if I don't call a function, is it generated inside the output executable?

It may be, that would depend on the compiler and scope of the function. More than likely it would be based on the optimisation level and whether or not the function is exported. For example static functions would probably not given an optimisation level to adhere to.

Your compiler documentation should be able to tell you, either than or run a few tests (examine generated assembly code for example).

If you use them for debug, then the common practice is to wrap them as macros that evaluate to nothing when called.

For example:

Code:

#ifdef DEBUG
#   define debug_myfunction(x) do { myfunction(x); } while(0)
#else
#   define debug_myfunction(x) do { } while(0)
#endif

11-24-2009, 06:35 AM	#1
Kempelen Registered User Join Date: Feb 2008 Posts: 107	About output size Hi, I use lots of functions to debug and for intermediate steps. When compiling, if I don't call a function, is it generated inside the output executable?
Kempelen is offline

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Help me please.	yann	C Programming	15	09-29-2009 09:04 PM
Stack around the variable 'Output' was corrupted	jacksb68	C Programming	5	09-08-2009 08:55 AM
[Tutorial] Implementing the Advanced Encryption Standard	KONI	C Programming	16	11-23-2007 01:48 PM
Error with a vector	Tropicalia	C++ Programming	20	09-28-2006 07:45 PM
File Size and File Size on Disk	DavidP	A Brief History of Cprogramming.com	4	12-15-2001 08:03 PM