You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, you can also compile directly without editing any makefile settings.
1006
+
2. Use the CMake option below to enable VPR profiler build.
1015
1007
```
1016
1008
make CMAKE_PARAMS="-DVTR_ENABLE_PROFILING=ON" vpr
1017
1009
```
1018
1010
1019
-
3. Now, whenever you run the VTR flow script, it will produce an extra file `gmon.out` that contains the raw profile information. First, run `gprof` to parse the info. You will need to specify the path to the `vpr` executable.
1011
+
3. With the profiler build, each time you run the VTR flow script, it will produce an extra file `gmon.out` that contains the raw profile information.
1012
+
Run `gprof` to parse this file. You will need to specify the path to the VPR executable.
1020
1013
```
1021
1014
gprof $VTR_ROOT/vpr/vpr gmon.out > gprof.txt
1022
1015
```
1023
1016
1024
-
4. Next, use `gprof2dot` to transform the results to a `.dot` or `.gv` file, which describes how your final profile results will look like. If you find the function names really long, specify the `-s` option for a clearer graph.
1017
+
4. Next, use `gprof2dot` to transform the parsed results to a `.dot` file, which describes the graph of your final profile results. If you encounter long function names, specify the `-s` option for a cleaner graph.
1025
1018
```
1026
1019
gprof2dot -s gprof.txt > vpr.dot
1027
1020
```
1028
1021
1029
-
5. You can chain the above commands to directly produce the final dot file:
1022
+
5. You can chain the above commands to directly produce the `.dot` file:
0 commit comments