|
|
|||
![]() PVS-Studio Static Code Analyzer for 64-bit and parallel C/C++ code
|
|||
![]() ![]() ![]() ![]() ![]()
02.09.2010
Feeling the new Intel Parallel Studio XE 2011 beta So I've gotten to try the C++ compiler included into Intel Parallel Studio XE 2011 beta at last.»
30.08.2010
Five days for fixing a two-character error, or a myth of almighty technologies aiding software development In this blog, you may often read posts about how this or that software tool or software development technology helps make fewer errors, find them faster and correct them easier.»
30.08.2010
d'Artagnan and Internet, or working on the problem of bad links Friends, it is high time we stopped considering links only in the context of their number and buying/ selling and counting PR of the site they are laid out on.» ![]()
22.07.2010
Using PVS-Studio with continuous integration systems This article illustrates techniques required to employ the use of PVS-Studio static code analyzer together with continuous integration systems.»
06.07.2010
Comparing capabilities of PVS-Studio and Visual Studio 2010 in detecting defects in 64-bit programs In the article, we will compare three mechanisms of code analysis from the viewpoint of detecting 64-bit errors: the Visual C++ 2010 compiler, the Code Analysis for C/C++ component included into Visual Studio 2010 and Viva64 analyzer included into PVS-Studio 3.60.»
29.06.2010
A Collection of Examples of 64-bit Errors in Real Programs
This article is the most complete collection of examples of 64-bit errors in the C and C++ languages.» ![]() |
64-bit Development![]() In this brief blog-note, Raymond Chen touches upon the AMD64 architecture and gives some tips on working with its registers supplying them with code samples.
One more brief blog-note by Raymond Chen where he explains the reasons why Win64 team chose LLP64 data model, showing by an example the rationality of their choice.
The paper deals with issues a developer may encounter when porting a 32-bit application to the x64 processor, and includes several sections devoted to explaining reasons for porting, giving some facts to consider before porting, and describing the steps of porting an application to a 64-bit platform. The paper covers only the most common points and rather briefly but it can serve a good introduction to porting 32-bit C++ applications to the x64 platform for those who has just faced this problem.
One of the main disadvantages of 32-bit computing is the limit of 4GB of memory leading to reduced performance of resource-intensive applications. The paper explains how to increase available virtual memory for 32-bit applications under 64-bit Windows with the help of Microsoft's 4GT method as the first step of making 32-bit applications ready for the port to a 64-bit platform. The author describes the principle of this method and gives some guidelines on how to use it to get the best result. Also, there is an additional section explaining the principles of coexistence of 32-bit and 64-bit applications in 64-bit Windows. The paper contains illustrative schemes, tables and code samples.
In this note, the author explains how to set Visual C++ 2008 Express Edition to be able to compile applications for 64-bit Windows with its help. The note provides thorough instructions and tips on how to use the compiler's abilities to a full extent. As the author says, though the decision he offers can be rather dangerous, still it is worth applying.
In this note, Kevin Frei tells about the differences between calling conventions of x86 and x64 architectures. His aim is to provide the programmers with the most important information about basic features of x64 calling convention: registers used, structure alignment, stack unwinding, etc. The note is supplied with links to resources containing more detailed materials.
|
||
|
© 2008 - 2010, OOO "Program Verification Systems"
300027, Russia, Tula, P.O. Box 1800. Office: Russia, Tula, Kutuzova 100-73 |
|||