Assessments - 0, GPA: 0
(
)
)
|
por este dispositivo também tem outras instruções :
Computadores - HP Integrity NonStop H-Series (16.73 mb)
Computadores - HP Integrity NonStop H-Series (957.56 kb)
Computadores - HP Integrity NonStop H-Series (881.66 kb)
Computadores - HP Integrity NonStop H-Series (965.62 kb)
Computadores - HP Integrity NonStop H-Series (676.93 kb)
Computadores - HP Integrity NonStop H-Series (393.72 kb)
Computadores - HP Integrity NonStop H-Series (776.57 kb)
Facilidade de uso
Building the Application
Understanding Code Coverage Concepts
Understanding Code Coverage Concepts
Code coverage reports are based on a model in which the application consists of
source files, which contain functions, which contain basic blocks. A basic block is a
sequence of code that is entered only at the beginning and exited at the end. Once
code enters a basic block, it executes the entire block unless an exception is raised
within the block. The Code Cover Utility considers a basic block to be covered if it is
entered, and also counts how many times such a block is entered during a test run.
Procedure calls within otherwise straight-line code are also considered block
boundaries. Therefore, the report tells when a procedure did not return to its caller,
because the block after the procedure call is uncovered, or has a smaller count than
the block leading up to the procedure call.
It is possible for multiple basic blocks to have the same source code location, with
some blocks covered and others not. The Code Cover Utility considers such locations
to be partially covered. For example, if overflow_traps is enabled, and your source
code contains a statement with an expression that could overflow when executed (but
never does), then that statement would be considered partially covered because the
basic blocks generated to handle the overflow for the statement are never executed
even though the expression for the statement is executed.
Certain sequences of straight-line code can result in multiple blocks; for example, if
statements can result in multiple blocks. In some cases, multiple blocks can result from
code generated by the compiler (and thus, not visible at the source level), such as a
check for overflow.
Using a different version of the compiler or running the compiler with different options,
such as different optimization levels, can result in different blocks being generated from
the same source code. For example, if the compiler determines that a block of source
code is never executed, it might not generate any object code for that source code.
Usage Considerations
For important information about characteristics and limitations of instrumented program
files and dynamic-link libraries (DLLs), see Compilation Issues on page 10-1.
Cleaning Up From Previous Code Coverage Runs
The first time you compile a program with the code-coverage option, the compiler
creates a SPI file. This SPI file is one of the input files to the codecov tool described in
Section 7, Running the Code Cover Utility. If compilation occurs in an OSS directory or
in a Windows folder, the name for the file is pgopti.spi. If compilation occurs in a
Guardian subvolume, the name for the file is pgospi. Subsequent compilations using
the codecov option within the same directory, folder, or subvolume update or add
information to this file.
Note. SPI files are used for code coverage only; they are not used for profile-guided
optimization.
HP Code Profiling Utilities Manual—542684-003
3 -2
... Este manual também é adequado para os modelos :
Computadores - HP Integrity NonStop J-Series (387.65 kb)