Thread overview
Long compilation
May 06, 2004
W³odzimierz Skiba
May 06, 2004
Arjan Knepper
May 06, 2004
W³odzimierz Skiba
May 06, 2004
Hi,

I heard and observed myself short times in compiling and building
applications with DMC. But recently I came to one source where building time
is extremly long and it happen to even fail with "No more free memory"-like message.
This is in one of files in wxWidgets unit tests. I have no much free time
to experiment with this file but I expect that the long time could be
avoided thanks to change in code. Currently it uses combination of #definitions,
stlport, c++. The problem I have is: what's easiest way apply similar process as
profiling application at run time but in relation to compilation ? Are there any
switches to compiler where I could output how many time compiler spends on some
parts of code ? Mentioned file is available here:

http://cvs.wxwidgets.org/viewcvs.cgi/wxWidgets/tests/strings/strings.cpp?rev=1.1&content-type=text/vnd.viewcvs-markup

ABX
May 06, 2004
I would start with compiling using the -v option.

Arjan

W³odzimierz Skiba wrote:
> Hi,
> 
> I heard and observed myself short times in compiling and building applications with DMC. But recently I came to one source where building time is extremly long and it happen to even fail with "No more free memory"-like message.
> This is in one of files in wxWidgets unit tests. I have no much free time to experiment with this file but I expect that the long time could be avoided thanks to change in code. Currently it uses combination of #definitions, stlport, c++. The problem I have is: what's easiest way apply similar process as profiling application at run time but in relation to compilation ? Are there any switches to compiler where I could output how many time compiler spends on some parts of code ? Mentioned file is available here:
> 
> http://cvs.wxwidgets.org/viewcvs.cgi/wxWidgets/tests/strings/strings.cpp?rev=1.1&content-type=text/vnd.viewcvs-markup
> 
> ABX
May 06, 2004
Arjan Knepper <arjan@ask.me> wrote in news:c7dc01$24mf$1@digitaldaemon.com:
> I would start with compiling using the -v option.

Whil this option itself isn't what I looked for, it allowed at least to preview output to gather feeling which function took majority of time. Patch #949276 delivered to wxWidgets, thanks.

ABX