projects
/
libreriscv.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
718ce7b
)
Remove width parameter from img tag
author
R Veera Kumar
<vklr@vkten.in>
Wed, 29 Jun 2022 13:33:11 +0000
(19:03 +0530)
committer
R Veera Kumar
<vklr@vkten.in>
Wed, 29 Jun 2022 13:33:11 +0000
(19:03 +0530)
openpower/sv/SimpleV_rationale.mdwn
patch
|
blob
|
history
diff --git
a/openpower/sv/SimpleV_rationale.mdwn
b/openpower/sv/SimpleV_rationale.mdwn
index a8096629b18718c165ebb339bdb52d952f6970cd..2fd44b8655a60de69b63678c5a3c0f2724f04691 100644
(file)
--- a/
openpower/sv/SimpleV_rationale.mdwn
+++ b/
openpower/sv/SimpleV_rationale.mdwn
@@
-903,7
+903,7
@@
definitely compelling enough to warrant in-depth investigation.
**Use-case: Matrix and Convolutions**
**Use-case: Matrix and Convolutions**
-<img src="/openpower/sv/sv_horizontal_vs_vertical.svg"
width=600
/>
+<img src="/openpower/sv/sv_horizontal_vs_vertical.svg" />
First, some important definitions, because there are two different
Vectorisation Modes in SVP64:
First, some important definitions, because there are two different
Vectorisation Modes in SVP64:
@@
-929,7
+929,7
@@
in full. Vertical-First may be used to perform a LD/ST within
the loop, covered by `svstep`, but it is still not ideal. This
is where the Snitch and EXTRA-V concepts kick in.
the loop, covered by `svstep`, but it is still not ideal. This
is where the Snitch and EXTRA-V concepts kick in.
-<img src="/openpower/sv/matrix_svremap.svg"
width=600
/>
+<img src="/openpower/sv/matrix_svremap.svg" />
Imagine a large Matrix scenario, with several values close to zero that
could be skipped: no need to include zero-multiplications, but a
Imagine a large Matrix scenario, with several values close to zero that
could be skipped: no need to include zero-multiplications, but a