Louis LeBlanc wrote:
I would have expected much different results. Shouldn't the file
sizes be smaller (at least a little) with the -O3 switch? Maybe
there's a loop unrolled to make it faster, resulting in a larger
codebase?
you generally expect -O3 files to be larger. inlining does not save
space. Indeed in the context of Ada, where well thought out inlining
is acheived by -O2 -gnatn (and the use of pragma Inline), we often
see -O3 executables being not only larger but slower, presumably due
to increased icache pressure.
The unoptimized version completed a 401,900 transaction test with no
problem. All day, I've been playing with different things,
there are many bugs, most notably uninitialed vars, that show
up only when you turn on optimization.
