Re: [Dev-C++] Runtime speed problem with later gcc compiler.

[Michal M. <mol...@se...>]

Hello,

Dne 24.8.2013 1:25, Lostgallifreyan napsal(a):
> (And the --help files I directed to text files say many things about optimisations
> but nothing about what 'n' might be or what sorts of groupings of optimisations might
> be done by those preset optimisers).

That's described in the GCC documentation:
http://gcc.gnu.org/onlinedocs/gcc-4.8.1/gcc/Optimize-Options.html#Optimize-Options

> My old command line was this: (Whole batch file..)
> 
> @ECHO OFF
> PATH=%PATH%;E:\CODING\GCC\BIN
> E:\CODING\GCC\BIN\WINDRES.EXE -Ocoff -IC:\WINDOWS\DESKTOP\TEST C:\WINDOWS\DESKTOP\TEST\FRAME.rc C:\WINDOWS\DESKTOP\TEST\FRAME.o
> E:\CODING\GCC\BIN\GCC.EXE -O3 --fast-math -IE:\Coding\gcc\include -IC:\WINDOWS\DESKTOP\TEST -mwindows C:\WINDOWS\DESKTOP\TEST\PHASEMOD.c C:\WINDOWS\DESKTOP\TEST\FRAME.o E:\CODING\GCC\LIB\libcomctl32.a E:\CODING\GCC\LIB\libwinmm.a -oC:\WINDOWS\DESKTOP\TEST\PHASEMOD.exe
> PHASEMOD.EXE

It looks like you don't strip debugging info from executable. You should
add -s option to the GCC command or call strip.exe on the build executable.

Regards,
Michal Molhanec