move image with resize to pdf-suitable location

diff --git a/openpower/simple_v_spec.tex b/openpower/simple_v_spec.tex
index cd688458d64343d6cb4141674a4a84c5a768fe6b..2fb766f6c30501fcd27f7707a94bce4e76e69baf 100644 (file)
--- a/openpower/simple_v_spec.tex
+++ b/openpower/simple_v_spec.tex
@@ -4,6 +4,7 @@
 \usepackage{lscape}
 \usepackage{sectsty}
 \usepackage{appendix}
+\usepackage{graphicx}
 \usepackage{anyfontsize}
 \usepackage{ifxetex,ifluatex}
 \usepackage{fixltx2e} % provides \textsubscript

diff --git a/openpower/sv/overview.mdwn b/openpower/sv/overview.mdwn
index 078521720ef328f484a6a47f2f91b9cc220c6f5c..24f1ec7f4f0b1a58339beace2fc96218c9eb3b09 100644 (file)
--- a/openpower/sv/overview.mdwn
+++ b/openpower/sv/overview.mdwn
@@ -381,6 +381,8 @@ This means that Vector elements start from locations specified by 64 bit
 "register" but that from that location onwards the elements *overlap
 subsequent registers*.
 
+![image](/svp64-primer/img/svp64_regs.svg){ width=40% }
+
 Here is another way to view the same concept, bearing in mind that it
 is assumed a LE memory order:
 
@@ -438,8 +440,6 @@ each element word:
 register number (`RT`, `RA`) indicates the *starting* point for the storage
 and retrieval of the elements.
 
-![image](/svp64-primer/img/svp64_regs.svg)
-
 Our simple loop, instead of accessing the array of regfile entries
 with a computed index `iregs[RT+i]`, would access the appropriate element
 of the appropriate width, such as `iregs[RT].s[i]` in order to access