Performance Validator will work with any portable executable (PE
) file format and supports .Net, .Net Core, C#, VB.Net, C, C++, Delphi, Fortran 95 and Visual Basic.
Microsoft .Net, .Net Core
Both .Net and .Net Core technologies are supported as well all the native compilers listed below.
The following compilers are supported by Performance Validator.
Microsoft http://www.microsoft.com
Performance Validator requires your application to be built using Microsoft® Visual Studio® 6.0 service pack 3 or later.
In practice, you may find that applications built with Developer Studio 4.2 and later can be used with Performance Validator.
•Microsoft Developer Studio 4.0
•Microsoft Developer Studio 5.0
•Microsoft Developer Studio 6.0
•Microsoft Visual Basic 6.0
•Microsoft Visual Studio 6.0 - service pack 3 or later
•Microsoft Visual Studio 7.0 / .net 2002
•Microsoft Visual Studio 7.1 / .net 2003
•Microsoft Visual Studio 8.0 / .net 2005
•Microsoft Visual Studio 9.0 / .net 2008
•Microsoft Visual Studio 10.0 / .net 2010
•Microsoft Visual Studio 11.0 / .net 2012
•Microsoft Visual Studio 12.0 / .net 2013
•Microsoft Visual Studio 14.0 / .net 2015
•Microsoft Visual Studio 15.0 / .net 2017
•etc...
Microsoft Developer Studio and Microsoft Visual Studio products support both C++ and Visual Basic.
Visual Studio and Visual Basic 6 in the Getting Started section.
Intel http://www.intel.com
•Intel performance compiler - The Intel compiler uses the Microsoft runtime already installed on your computer rather than supply its own
•Intel Fortran
Intel use Microsoft's PDB proprietary symbol information format. If your compiler uses PDB symbol information Performance Validator will be able to use it.
Metrowerks
•Metrowerks CodeWarrior for Windows Version 8.0
•Metrowerks CodeWarrior for Windows Version 9.0
You will need to ensure the debug information is stored as CodeView information and not a custom Metrowerks debug format. Metrowerks symbolic information is embedded in the .exe/.dll as CodeView information. Please consult the documentation for CodeWarrior to include debug information (including filenames and line numbers) in the CodeView information.
Embarcadero https://www.embarcadero.com/
This includes compilers formerly produced by Borland.
•C++ Builder 5.0 to C++ Builder 11
•Delphi 6.0 to Delphi 11
•Rad Studio
C++ Builder and Delphi in the Getting Started section.
MinGW http://www.mingw.org
•MinGW (Minimalist GNU for Windows)
MinGW can create symbols in a variety of formats. If you configure MinGW to produce DWARF symbols, STABS symbols or COFF symbols Performance Validator can read them.
MinGW compiler in the Getting Started section.
Qt (Digia, Nokia, Trolltech) http://qt.io
•QtCreator
Ensure that debug information is created in DWARF, STABS or COFF formats.
Salford Software now maintained by SilverFrost
•Salford Software Fortran 95
Salford Software Fortran 95 uses COFF symbol information. If your compiler uses COFF symbol information Performance Validator will be able to use that information.
Compaq
•Compaq Visual Fortran 6.6
The Compaq Visual Fortran product may be compatible with Performance Validator. If you are using Compaq Visual Fortran and wish to use Performance Validator please contact us.
Other...?
If the compiler you are using is not listed here, please contact us for advice. We add compilers as we receive requests for them. In fact, the C++ Builder, Delphi, Metrowerks CodeWarrior, Salford Software's Fortran 95 compiler, and Intel Fortran support were all added at the request of customers.
