Re[2]: IFS Kit and Visual Studio 2005

NTFSD
1

> However, we should use better arguments than rumors about compiler

incompatibilities.

This is kinda off-topic, but still:

Once, I had a source code, compiled with the WDK 6000.
One of the functions within was compiled totally wrong.

Just for imagination, “totally wrong” means there were
calls to different functions than written in the sources.

Three of my colleagues have confirmed that it is not
a wrong macro or a weird bug (no macros, no defines that
could have changed the functions called).

I have converted the project from WDK 6000 makefile to
VS 2005 project, and voila - the code was compiled the same
*wrong* way. The only condition was using the /O2 flag
(Maximize Speed), switching to /O1 (Minimize Size)
caused the compiled EXE to be correct in both WDK and VS2005
builds.

So the compatibility between WDK compiler and VS 2005
compiler was pretty good :-))

L.

2

Hum! Long time ago I saw the same compiler behaviour: I had two
different functions and running the driver it was ever called the same
function. Really, in my case, they weren’t exactly ‘different’
functions. Their codes were equivalent and compiler optimized using only
one of them.

Gonzalo.

-----Mensaje original-----
De: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] En nombre de Ladislav Zezula
Enviado el: domingo, 20 de mayo de 2007 16:49
Para: Windows File Systems Devs Interest List
Asunto: Re[2]: [ntfsd] IFS Kit and Visual Studio 2005

However, we should use better arguments than rumors about compiler
incompatibilities.

This is kinda off-topic, but still:

Once, I had a source code, compiled with the WDK 6000.
One of the functions within was compiled totally wrong.

Just for imagination, “totally wrong” means there were
calls to different functions than written in the sources.

Three of my colleagues have confirmed that it is not
a wrong macro or a weird bug (no macros, no defines that
could have changed the functions called).

I have converted the project from WDK 6000 makefile to
VS 2005 project, and voila - the code was compiled the same
*wrong* way. The only condition was using the /O2 flag
(Maximize Speed), switching to /O1 (Minimize Size)
caused the compiled EXE to be correct in both WDK and VS2005
builds.

So the compatibility between WDK compiler and VS 2005
compiler was pretty good :-))

L.

Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@pandasoftware.es
To unsubscribe send a blank email to xxxxx@lists.osr.com