Add example for vec_bperm #48

Merged
ThinkOpenly merged 1 commits from vec_bperm_be into master 4 years ago
ThinkOpenly commented 4 years ago (Migrated from github.com)

vec_bperm is a challenge for showing an example using just tables,
but I've made an attempt.

Three tables are used:

  • The values of the input vectors a and b.
  • A zoomed in view of the last two bytes of a and the bit
    manipulations therein that leads to the intermediate result.
  • The result vector r.

Only one example has been provided, but it's getting big.

Fixes #14.

  • PDF:
    Screenshot from 2020-05-07 20-30-24
  • web:
    Screenshot from 2020-05-07 20-29-58

Signed-off-by: Paul A. Clarke pc@us.ibm.com

vec_bperm is a challenge for showing an example using just tables, but I've made an attempt. Three tables are used: - The values of the input vectors *a* and *b*. - A zoomed in view of the last two bytes of *a* and the bit manipulations therein that leads to the intermediate result. - The result vector *r*. Only one example has been provided, but it's getting big. Fixes #14. * PDF: ![Screenshot from 2020-05-07 20-30-24](https://user-images.githubusercontent.com/12301795/81360556-d1aafd80-90a1-11ea-8a17-21d76c2fbe86.png) * web: ![Screenshot from 2020-05-07 20-29-58](https://user-images.githubusercontent.com/12301795/81360564-d96aa200-90a1-11ea-9879-45eb6ee7e1ef.png) Signed-off-by: Paul A. Clarke <pc@us.ibm.com>
wschmidt-ibm commented 4 years ago (Migrated from github.com)

This is correct, except for one piece of confusion.

The part that says "bit indices b[i] (0 <= i < 16), ([70..7F])" makes it seem like b is a little-endian vector, as those numbers appear from right-to-left, not left-to-right. I would prefer that you write (7F, 7E, ..., 70) for clarity. Otherwise looks good with that change.

Thanks!

This is correct, except for one piece of confusion. The part that says "bit indices b[i] (0 <= i < 16), ([70..7F])" makes it seem like b is a little-endian vector, as those numbers appear from right-to-left, not left-to-right. I would prefer that you write (7F, 7E, ..., 70) for clarity. Otherwise looks good with that change. Thanks!
The pull request has been merged as 24953643b8.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b vec_bperm_be master
git pull origin vec_bperm_be

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff vec_bperm_be
git push origin master
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: systemsoftware/Programming-Guides#48
Loading…
There is no content yet.