Using 2003 Toolkit to optimize - but file sizes same?

[noleander]

I'm trying to get Vis C++ std to compile using /O2 optimizing flag. Many
people have suggested downloading the MS C++ 2003 Toolkit ... it supposedly
has C++ compiler bins that one could use.

I downloaded the 2003 Toolkit ... but the bin files are identical (size,
date, contents) as my existing Vis C++ compiler. I have listed the file
sizes below.

Can someone who has downloaded the 2003 Toolkit see what file sizes and fiel
dates they have?

Here are the 2003 Toolkit files from Toolkit/bin:

3/18/2003 21:11 933,888 c1.dll
3/18/2003 21:11 2,207,744 c1xx.dll
3/18/2003 21:12 1,867,776 c2.dll
3/18/2003 20:37 86,016 cl.exe

Here are my original Vis C++ Std files from Vis C++ .NET/Vc7/bin

3/18/2003 20:11 933,888 c1.dll
3/18/2003 20:11 2,207,744 c1xx.dll
3/18/2003 19:37 823,296 c2.dll
3/18/2003 19:37 81,920 cl.exe
3/15/2003 0:46 145 cl.exe.config

And to answer the obvious question: No, I did not copy the files from the
Toolkit folder to the Vc7/bin folder. I did a "diff" and the files are
identical.

In any case, when I compile with Vis C++ and I add the /O2 option to the
compiler command line, it gives a warning "optimization not supported by
Standard edition".

Thanks in advance for any help,
neal

[Carl Daniel [VC++ MVP]]

noleander wrote:

I'm trying to get Vis C++ std to compile using /O2 optimizing flag.
Many people have suggested downloading the MS C++ 2003 Toolkit ...
it supposedly has C++ compiler bins that one could use.

I downloaded the 2003 Toolkit ... but the bin files are identical
(size, date, contents) as my existing Vis C++ compiler. I have
listed the file sizes below.

Can someone who has downloaded the 2003 Toolkit see what file sizes
and fiel dates they have?

Here are the 2003 Toolkit files from Toolkit/bin:

3/18/2003 21:11 933,888 c1.dll
3/18/2003 21:11 2,207,744 c1xx.dll
3/18/2003 21:12 1,867,776 c2.dll ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3/18/2003 20:37 86,016 cl.exe

Here are my original Vis C++ Std files from Vis C++ .NET/Vc7/bin

3/18/2003 20:11 933,888 c1.dll
3/18/2003 20:11 2,207,744 c1xx.dll
3/18/2003 19:37 823,296 c2.dll ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3/18/2003 19:37 81,920 cl.exe
3/15/2003 0:46 145 cl.exe.config

Note the difference in size for c2.dll. That's the compiler "back end" and
contains the optimizer.

-cd

PS:

c1.dll - 'C' front end
c1xx.dll - 'C++' front end
c2.dll - back end
cl.exe - compiler driver
cl.exe.config - config file for cl.exe (specifies the version of the managed
runtime targeted by the compiler).

-cd

[Jochen Kalmbach]

noleander wrote:

In any case, when I compile with Vis C++ and I add the /O2 option to the
compiler command line, it gives a warning "optimization not supported by
Standard edition".

You should note, that this message will not disappear if you use the
Toolkit compiler... You will still get the same message, but if you
specify /O2 it will optimize.

--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/