Some time ago, we wrote several letters to Embarcadero offering them to collaborate with us and use our tools to test 64-bit C/C++ code. Our idea was to integrate PVS-Studio with C++Builder or implement some diagnosis rules right in their compiler. All the letters remained without answer and that is why we decided to post a brief note for those who would be interested in the topic of testing the code created in C++Builder on efficiency on 64-bit systems.
OpenMP support in PVS-Studio had been dropped after version 5.20. If you have any questions, feel free to contact our support.
At present, PVS-Studio package consists of two static code analyzers: Viva64 to search for 64-bit errors and VivaMP to test parallel OpenMP programs. PVS-Studio integrates into Microsoft Visual Studio 2005/2008 development environment and MSDN Help system.
At the moment of writing this text, PVS-Studio does not support C++Builder by Embarcadero and perhaps it is too early to think about it. The time of 64-bit programs for Embarcadero C++Builder users will come a bit later. However, creating 64-bit applications is a relevant task. We are ready to discuss the question of integrating PVS-Studio with Embarcadero C++Builder.
If your company has a large amount of source code and is planning to adapt it for 64-bit systems, please write to our support service. We are a small company that can quickly respond to clients' needs and implement all the necessary functionality and support.
A developer who is porting his Windows-application to the 64-bit platform sent a letter to our support service with a question about using floating-point calculations. By his permission we publish the answer to this question in the blog since this topic might be interesting for other developers as well.
We have already written in our articles about one of the problems of code migration to 64-bit systems relating to incorrect overload of virtual functions. For example, our article "20 issues of porting C++ code on the 64-bit platform" was published in March, 2007 (although is still relevant). It described the issue of virtual functions.