Closed johanpel closed 4 years ago
Merging #203 into develop will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## develop #203 +/- ##
========================================
Coverage 88.03% 88.03%
========================================
Files 50 50
Lines 4906 4906
========================================
Hits 4319 4319
Misses 587 587
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 5c194a8...0502992. Read the comment docs.
While restructuring this includes a fix for #201
Merging #203 into develop will not change coverage. The diff coverage is
100%
.
@@ Coverage Diff @@
## develop #203 +/- ##
========================================
Coverage 88.03% 88.03%
========================================
Files 50 50
Lines 4906 4906
========================================
Hits 4319 4319
Misses 587 587
Impacted Files | Coverage Δ | |
---|---|---|
hardware/arrays/ArrayWriter.vhd | 95.12% <ø> (ø) |
:arrow_up: |
hardware/interconnect/BusWriteBuffer.vhd | 96% <ø> (ø) |
:arrow_up: |
hardware/arrays/test/arraywriter/prim32_epc_tc.vhd | 96.96% <ø> (-0.02%) |
:arrow_down: |
hardware/interconnect/BusWriteArbiterVec.vhd | 98.87% <ø> (-0.02%) |
:arrow_down: |
hardware/arrays/Array_pkg.vhd | 100% <ø> (ø) |
:arrow_up: |
...dware/arrays/test/arraywriter/listprim8epc4_tc.vhd | 98.17% <ø> (ø) |
:arrow_up: |
hardware/buffers/BufferWriter.vhd | 99.11% <ø> (ø) |
:arrow_up: |
hardware/arrays/test/arraywriter/prim32_tc.vhd | 96.93% <ø> (ø) |
:arrow_up: |
hardware/arrays/ArrayWriterLevel.vhd | 77.27% <ø> (ø) |
:arrow_up: |
hardware/interconnect/test/BusChecking_pkg.vhd | 100% <ø> (ø) |
:arrow_up: |
... and 18 more |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update bf33503...ea1f525. Read the comment docs.
The original goal of this PR was to add stream profiling, but I fixed a whole bunch of stuff with it to make that and some future improvements easier.
With this profiling addition, users can profile their applications and discover the utilization of streams during run-time. For now it is supported in the generate design and simulation path, but the run-time library should probably still implement some facility for it.