There are a couple of classes of misuse of "pseudo" within the document that conflict with uses elsewhere in the overall RISC-V ISA Specification:
All uses of "pseudo-ops" should instead be "pseudoinstructions" (all in doc/scalar/riscv-crypto-scalar-appx-rationale.adoc):
of grevi be implemented, which can be invoked via their pseudo-ops.
The zip and unzip pseudo-ops are specific instances of
pseudo-ops.
Note that this makes it even harder to find pseudoinstructions than it already is.
"pseudosomething" sometimes has a space or hyphen separating "pseudo" from the rest of the word. We should pick one usage. I think the most common is with no separation. "pseudorandom" is in
the dictionary, for example:
doc/scalar/riscv-crypto-scalar-zkt.adoc:
Recall that rev, zip and unzip are pseudo-instructions representing
"MOVEit Crypto is a compact and fast dynamically-linked library for Windows and Linux. It provides AES encryption, SHA-1 and SHA-2 hashing, and pseudo-random number generation. Both 32-bit and 64-bit versions are available for each operating system. MOVEit Crypto is a member of the MOVEit security and file transfer product family."
"The Encryption Plus Crypographic Library (EPCL) is a compact and fast encryption library that provides an Application Programming Interface (API) featuring NIST Approved AES encryption, SHA-1 hashing, and pseudo-random generation."
"MOVEit Crypto is a compact 32-bit dynamically linked library (DLL) that provides encryption services to applications running on Microsoft Windows operating systems. The module provides an API featuring the latest NIST-approved encryption, hashing, and pseudo-random number generation algorithms."
doc/riscv-crypto-spec.bib
title = {A Simple Unpredictable Pseudo-Random Number Generator},
doc/supp/gcm-mode-cmul.adoc
the GREV[W] instruction with constant 7 (pseudo-instruction rev)
tools/opcodes-crypto-scalar-both
# Poll Entropy / Get Noise Pseudo Instructions
tools/gcc-patch-tasks.adoc
Additionally, there are two pseudo instructions defined, which alias
There are a couple of classes of misuse of "pseudo" within the document that conflict with uses elsewhere in the overall RISC-V ISA Specification:
All uses of "pseudo-ops" should instead be "pseudoinstructions" (all in
doc/scalar/riscv-crypto-scalar-appx-rationale.adoc
):Note that this makes it even harder to find pseudoinstructions than it already is.
"pseudosomething" sometimes has a space or hyphen separating "pseudo" from the rest of the word. We should pick one usage. I think the most common is with no separation. "pseudorandom" is in the dictionary, for example:
doc/scalar/riscv-crypto-scalar-zkt.adoc
:doc/vector/riscv-crypto-vector-sail-specifications.adoc
:doc/vector/code-samples/nist-kat/KAT_AES/aesval.html
doc/riscv-crypto-spec.bib
doc/supp/gcm-mode-cmul.adoc
tools/opcodes-crypto-scalar-both
tools/gcc-patch-tasks.adoc
tests/compliance/test-plan-scalar.adoc