Re^2: Is your Perl running as fast as possible?

among things discussed on p5p, I remember it was mentioned that some RedHat distributions go with DEBUG-enabled builds of perl, which is rather sad.

What's bad about running a debug enabled perl? Are you worried about a microscopic increase in the size of the perl binary caused by debugging symbols? Is there something else I should be aware of?

Comment on Re^2: Is your Perl running as fast as possible?

Replies are listed 'Best First'.
Re^3: Is your Perl running as fast as possible? by perrin (Chancellor) on Oct 17, 2005 at 19:16 UTC
It's a little slower. Compiling for threads make it a lot slower.	[reply]
Re^4: Is your Perl running as fast as possible? by Courage (Parson) on Oct 18, 2005 at 07:24 UTC
not only "debug symbols" that binary will contain, it will also contain code within some #ifdef's; yet some -Oxxx are disabled Let's RTFS a bit -- following is an excerpt from ./win32/makefile.mk (same for linux build, I guess) `# # uncomment next line if you want debug version of perl (big,slow) # If not enabled, we automatically try to use maximum optimization # with all compilers that are known to have a working optimizer. # #CFG *= Debug` [download]	[reply] [d/l]