... | ... | @@ -3,13 +3,16 @@ How to Run Code Coverage Analysis |
|
|
|
|
|
ICC
|
|
|
---
|
|
|
* Build the code as normal with the `-prof-gen=srcpos` compiler flag.
|
|
|
* Run the test/simulation as normal and this should generate a `.dyn` file, which contains dynamic profile information.
|
|
|
* Use the `profmerge` tool to merge all `.dyn` files into one `.dpi` file. This can merge multiple `.dyn` from successive runs of the application with different runtime parameters (e.g. running `test27cells` with varying number of particles per cell):
|
|
|
* Build the code as normal with the `-prof-gen=srcpos -prof-dir=PATH_TO_PROF_DIR/prof-info` compiler flag. Where `PATH_TO_PROF_DIR` is the path to a directory that you have created to store the profiling information.
|
|
|
* Run the test/simulation as normal and this should generate a `.dyn` file in `prof-info`, which contains dynamic profile information.
|
|
|
* Navigate to the `prof-info` directory.
|
|
|
* Use the `profmerge` tool to merge all `.dyn` files into one `.dpi` file. This merges multiple `.dyn` from successive runs of the application with different runtime parameters (e.g. running `test27cells` with varying number of particles per cell):
|
|
|
|
|
|
```
|
|
|
profmerge -a
|
|
|
```
|
|
|
(Note: If you only want code coverage from the last test run remove old `.dyn` files and the `.dpi` file in the `prof-info` directory. As old test runs might cover code that was not covered in the latest test run.)
|
|
|
|
|
|
* Run the code coverage tool and specify the path to SWIFT library `.spi` file:
|
|
|
|
|
|
```
|
... | ... | |