Intel® Performance Bottleneck Analyzer

Zero Length Calls

TITLE: Zero Length Calls ISSUE_NAME: ZERO_LENGTH_CALL DESCRIPTION: A “zero length call” uses the attribute of the call instruction to push the immediate instruction pointer on to the stack and then pops off that address into a register. This is accomplished without any matching return on the call.  This code construct is also commonly referred to as a zero displacement call. RELEVANCE:

Instruction Starvation

TITLE: Instruction Starvation ISSUE_NAME: InstructionStarvation DESCRIPTION:  Execution stalls because the front-end fails to deliver instructions. This metric is the ratio of cycles generated when no instruction was issued by the front-end to all cycles. Such stalls are called Instruction Starvation, and may be due to a large code working set size or a high degree of branch misprediction, which can cause a large number of L1I misses. RELEVANCE: Negatively impacts performance as the execution is stalled as it waits for instructions to be delivered by the fronted.  EXAMPLE:  SOLUTION:

Instructions Retired Per Clock Cycle

TITLE: Instructions Retired Per Clock Cycle ISSUE_NAME: InstructionsPerClock DESCRIPTION:  The ratio of instructions retired per clock cycle (IPC). RELEVANCE: Higher instructions retired per cycle is typically desirable because it represents a larger amount of work being complete in a given unit of time. EXAMPLE:  SOLUTION: RELATED_SOURCES: NOTES:

x87 Floating Point Store/Restore for Rounding

TITLE: x87 Floating Point Store/Restore for Rounding ISSUE_NAME: X87_ROUNDING DESCRIPTION: x87 floating point calculations store/restore from stack to round to 32-bit (single precision) or 64-bit (double precision) RELEVANCE: Negatively impacts most architectures on all OSs but costsAtom's Bonnell, Silverthorne and Saltwell (10-12 cycles) since they cannot store cannot be forwarded to loads in the FP domain. EXAMPLE: Here is an example of how x87 math is done with rounding done by storing/restoring from memory in between calculations: fadd fstp [address]

ERROR: Dump file generated for ... is invalid

Does anyone know of workrounds or diagnostics for invalid dump files? The only thing I've seen is a comment to avoid older VTune installation licenses appearing on the "path" and a problem with xed.exe that should now be fixed. On my machine I don't have older vtune information anywhere in the environment or license file, and the data collecting phase proceeded without errors, yet I get an erroras below.

C:\\tmp\\fipde\\pba>java -Xmx1000m xIFJava.Main f "foo.QAG" -jdir "tb5" -NHM

Intel Performance Bottleneck Analyzer - Version 4.0.1 RC3

Pages

Subscribe to Intel® Performance Bottleneck Analyzer