Add simple examples for `vec_unsignede` and `vec_unsignedo`,
making sure to show undefined results and negative truncation.
Fixes#29.
Signed-off-by: Paul A. Clarke <pc@us.ibm.com>
`vec_permxor` is complex enough to warrant an example.
The table used is very wide. I squeezed it more by changing the names
of `index1` and `index2` to `x` and `y`, respectively.
Note: The table may still be too wide, as some additional warnings are
now generated during `mvn generate-sources`:
```
WARNING: Line 1 of a paragraph overflows the available area by more than 50 points. (See position 1:-1)
Apr 30, 2020 8:44:03 PM org.apache.fop.events.LoggingEventListener processEvent
WARNING: Line 1 of a paragraph overflows the available area by 468 millipoints. (See position 14259:-1)
Apr 30, 2020 8:44:03 PM org.apache.fop.events.LoggingEventListener processEvent
...
WARNING: span="inherit" on fo:block, but no explicit value found on the parent FO.
```
Fixes#20.
Signed-off-by: Paul A. Clarke <pc@us.ibm.com>
vec_vslv and vec_vsrv are confusing in their own right and even more
so because they operate only with big-endian semantics.
Some examples are warranted.
Note that the respective examples are arranged such that the impact of
shifting in zero bits has a visible impact.
Signed-off-by: Paul A. Clarke <pc@us.ibm.com>
The "Vector Registers as Part of VSRs" figure was very large,
especially as it immediately follows an almost identical figure.
Before this change:
fig-fpr-vsr.png: PNG image data, 663 x 300...
fig-vr-vsr.png: PNG image data, 1367 x 608...
After this change:
fig-fpr-vsr.png: PNG image data, 663 x 300...
fig-vr-vsr.png: PNG image data, 645 x 287...
I chose this size because the actual side boundaries of the
table most closely match in size.
The scaling, using The GIMP, resulted in somewhat blurry lines,
but still quite clear enough, and good enough.
Signed-off-by: Paul A. Clarke <pc@us.ibm.com>
Paul Clarke
Bill Schmidt