This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository gcc.
from 23224f06c98 RISC-V: Support FP SGNJX autovec for VLS mode
new a1751681867 RISC-V: Make bit manipulation value / round number and shif [...]
new 9882b81410f RISC-V: Make SHA-256, SM3 and SM4 builtins operate on uint32_t
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
gcc/config/riscv/crypto.md | 161 ++++++++++++++-------
gcc/config/riscv/riscv-builtins.cc | 14 +-
gcc/config/riscv/riscv-cmo.def | 16 +-
gcc/config/riscv/riscv-ftypes.def | 23 ++-
gcc/config/riscv/riscv-scalar-crypto.def | 96 ++++++------
gcc/testsuite/gcc.target/riscv/zbc32.c | 6 +-
gcc/testsuite/gcc.target/riscv/zbc64.c | 6 +-
gcc/testsuite/gcc.target/riscv/zbkb32.c | 10 +-
gcc/testsuite/gcc.target/riscv/zbkb64.c | 8 +-
gcc/testsuite/gcc.target/riscv/zbkc32.c | 4 +-
gcc/testsuite/gcc.target/riscv/zbkc64.c | 4 +-
gcc/testsuite/gcc.target/riscv/zbkx32.c | 4 +-
gcc/testsuite/gcc.target/riscv/zbkx64.c | 4 +-
gcc/testsuite/gcc.target/riscv/zknd32.c | 4 +-
gcc/testsuite/gcc.target/riscv/zknd64.c | 10 +-
gcc/testsuite/gcc.target/riscv/zkne32.c | 4 +-
gcc/testsuite/gcc.target/riscv/zkne64.c | 8 +-
gcc/testsuite/gcc.target/riscv/zknh-sha256-32.c | 10 ++
.../riscv/{zknh-sha256.c => zknh-sha256-64.c} | 8 +-
gcc/testsuite/gcc.target/riscv/zknh-sha512-32.c | 12 +-
gcc/testsuite/gcc.target/riscv/zknh-sha512-64.c | 8 +-
gcc/testsuite/gcc.target/riscv/zksed32.c | 4 +-
gcc/testsuite/gcc.target/riscv/zksed64.c | 4 +-
gcc/testsuite/gcc.target/riscv/zksh32.c | 4 +-
gcc/testsuite/gcc.target/riscv/zksh64.c | 4 +-
25 files changed, 247 insertions(+), 189 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/riscv/zknh-sha256-32.c
rename gcc/testsuite/gcc.target/riscv/{zknh-sha256.c => zknh-sha256-64.c} (79%)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.