Reviews

  • Mike Wall. Porting and Optimizing Applications on 64-bit Windows for AMD64 Architecture

    13.03.2012
    Mike Wall concentrates upon the aspect of optimizing and boosting performance of code during porting. Starting with an explanation of AMD64 architecture's advantages, the author discusses several methods of increasing code's performance including use of compiler switches, intrinsic functions, assembly and many more. In addition he also describes advantages of using CodeAnalyst tool when optimizing the code. In the article you will find some useful examples of code.

  • Bruce Dawson. 64-Bit Made Easy

    14.02.2012
    In his post, Bruce Dawson explains what technique he and his Valve team use to find and fix 64 bits related pointer truncation bugs. A code sample is taken as an example.

  • Christian Holler. Trying new code analysis techniques

    27.01.2012
    In this short post, the author tells us about his experience of using two static analysis tools each of which provides its own technique - Address Sanitizer (ASan) and Clang Static Analyzer.

  • Remah. 32-bit and 64-bit explained

    11.01.2012
    The article explains the differences between 32-bit and 64-bit systems from the viewpoint of the entire system structure consisting of three components or levels: CPU, operating system and applications. The basic principles of architectural arrangement are explained, and the common questions about 32-bit and 64-bit systems are addressed.

  • Jim Bird. Static Analysis isn't Development Testing

    06.01.2012
    The post focuses on the false idea that static analysis tools are testing tools or can be a good substitute for them. The author explains the difference between various kinds of testing and static analysis bringing out the point of the latter and its role in development. He agrees that static analyzers are necessary tools, but they are intended for detecting a "narrow band of code-related defects".

  • Frank Kim. Seven Tips for Picking a Static Analysis Tool

    13.12.2011
    This short post gives you some tips about how to choose a static analysis tool for your projects. Following these tips will help you to maximize your choice.

  • Christian Wojner. WOW-Effect

    30.11.2011
    The WOW layer present in the 64-bit Windows and the redirection mechanism it employs causes troubles for IT-security tests. The article explains the nature of these troubles and tells how to adapt existing analysis tools to handle this issue.

  • Development Testing with Static Analysis

    07.11.2011
    The post refers us to an article by Coverity describing the benefits of static analysis and mentioning three analysis techniques it can provide: dataflow analysis, interprocedural analysis and false-path pruning. Each of this technique is illustrated by a code sample.

  • Bojan Komazec. 32-bit and 64-bit versions of Windows C++ application

    06.10.2011
    The author uses a sample code to show how to set compiler and linker options to build a C++ application for 64-bit Windows. Each step is commented upon.

  • Arthur Hicken. What is Static Analysis... and What is it Good For?

    05.10.2011
    Static analysis includes many techniques each of which helps developers to find various bugs and issues at different stages of the development process. In his article, Arthur Hicken describes these techniques (peer code review, pattern based analysis, flow analysis, metrics, compiler/build output) and the types of problems they are meant to solve.