Software correctness tools should be a core component of any quality assurance (QA) program, and the Intel® Inspector XE provides functionality your QA department can use to simplify getting the answers it needs.
Tools and Options to Consider for QA
What can you do if you suspect that you have memory violations on the stack?
Stack memory issues are usually not a problem for most users, so the Intel Inspector XE does not enable this expensive functionality by default. However, if you need to check for these issues, you can use a custom analysis to enable this functionality.
Consider the following code where all local variables in a function are created in stack and go out of scope when the function returns. So you would expect to see a memory issue.
When you profile your software with VTune™ Amplifier XE you often start from looking at the top function hotspots list. This allows you to see what functions are spending CPU resources, so you can focus your optimization efforts.
Function call counts can provide some additional information to assist in further optimization.
If you are new to Cilk™ Plus, you have probably been impressed by how easy it is to turn a serial program into a parallel program. You’ve also realized, though, that adding
cilk_for to a program doesn’t automatically solve the harder parts of parallel programming: dealing with data races, and coordinating work that is done in parallel.
Intel® MKL provides the general purpose BLAS* matrix multiply routines ?GEMM defined as follows:
C := alpha*op(A)*op(B) + beta*C
where alpha and beta are scalars, op(A) is an m-by-k matrix, op(B) is a k-by-n matrix, C is an m-by-n matrix, with op(X) being either X, or XT, or XH.