Paul Clarke
24953643b8
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. Signed-off-by: Paul A. Clarke <pc@us.ibm.com> |
5 years ago | |
|---|---|---|
| .. | ||
| figures | 7 years ago | |
| Byte-array-endian.png | 5 years ago | |
| LICENSE | 7 years ago | |
| README.md | 7 years ago | |
| Scalar-endian.png | 5 years ago | |
| Word-array-endian.png | 5 years ago | |
| app_template.xml | 7 years ago | |
| bk_main.xml | 5 years ago | |
| ch_biendian.xml | 5 years ago | |
| ch_example.xml | 7 years ago | |
| ch_intro.xml | 5 years ago | |
| ch_isa_intrin_xref.xml | 5 years ago | |
| ch_scal_reference.xml | 7 years ago | |
| ch_techniques.xml | 5 years ago | |
| ch_template_overview.xml | 7 years ago | |
| ch_vec_reference.xml | 5 years ago | |
| fig-fpr-vsr.png | 5 years ago | |
| fig-vr-vsr.png | 5 years ago | |
| pom.xml | 5 years ago | |
| vgbbd.png | 5 years ago | |
README.md
OpenPOWER Foundation Documentation Development Guide
This repository holds the source for the documentation development guide (formerly Master Template Document) for OpenPOWER Foundation. The PDF and HTML generated from the doc/template/ directory build a document that both describes how to build a new document and contains examples and directions on how to do it.
To build this project, one must ensure that the Docs-Master project has also been cloned at the same directory level as the Docs-Template project. This can be accomplished with the following steps:
- Clone the master documentation project (Docs-Master) using the following command:
$ git clone https://github.com/OpenPOWERFoundation/Docs-Master.git
- Clone this project (Docs-Template) using the following command:
$ git clone https://github.com/OpenPOWERFoundation/Docs-Template.git
- Build the project with these commands:
$ cd Docs-Template
$ mvn clean generate-sources
The online version of the document can be found in the OpenPOWER Foundation Document library at OpenPOWER Foundation Documentation Development Guide.
The project which controls the look and feel of the document is the
Docs-Maven-Plugin project, an
OpenPOWER Foundation private project on GitHub. To obtain access to the Maven Plugin project,
contact Jeff Scheel [scheel@us.ibm.com](mailto://scheel@us.ibm.com) or
Jeff Brown [jeffdb@us.ibm.com](mailto://jeffdb@us.ibm.com).
License
This project is licensed under the Apache V2 license. More information can be found in the LICENSE file or online at
http://www.apache.org/licenses/LICENSE-2.0
Contributions
To contribute to the OpenPOWER Foundation template document project, contact Jeff Scheel [scheel@us.ibm.com](mailto://scheel@us.ibm.com) or
Jeff Brown [jeffdb@us.ibm.com](mailto://jeffdb@us.ibm.com).
Contributions to this project should conform to the Developer Certificate of Origin as defined at http://elinux.org/Developer_Certificate_Of_Origin.
Commits to this project need to contain the following line to indicate
the submitter accepts the DCO:
Signed-off-by: Your Name <your_email@domain.com>
By contributing in this way, you agree to the terms as follows:
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
660 York Street, Suite 102,
San Francisco, CA 94110 USA
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.