-*- mode: troff; coding: utf-8 -*-
Automatically generated by Pod::Man v6.0.2 (Pod::Simple 3.45)

Standard preamble:
========================================================================
..

..

.. \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
. ds C` "" . ds C' "" 'br\} . ds C` . ds C' 'br\}
Escape single quotes in literal strings from groff's Unicode transform.

If the F register is >0, we'll generate index entries on stderr for
titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
entries marked with X<> in POD. Of course, you'll have to process the
output yourself in some meaningful fashion.

Avoid warning from groff about undefined register 'F'.
.. .nr rF 0 . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF
Required to disable full justification in groff 1.23.0.
========================================================================

Title "OPENSSL_PPCCAP 3ossl" For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.
OPENSSL_ppccap - the PowerPC processor capabilities vector Header "SYNOPSIS" .Vb 1 env OPENSSL_ppccap=... <application> .Ve Header "DESCRIPTION" libcrypto supports PowerPC instruction set extensions. These extensions are represented by bits in the PowerPC capabilities vector. When libcrypto initializes, it stores the results returned by PowerPC CPU capabilities detection logic in the PowerPC capabilities vector. The CPU capabilities detection methods are OS-dependent and use a combination of information gathered by the kernel during boot and probe functions that attempt to execute instructions and trap illegal instruction signals with a signal handler.

To override the set of extensions available to an application, you can set the \fBOPENSSL_ppccap environment variable before you start the application. The environment variable is assigned a numerical value that denotes the bits in the PowerPC capabilities vector. The ppc_arch.h header file states that, "Flags\*(Aq usage can appear ambiguous, because they are set rather to reflect OpenSSL performance preferences than actual processor capabilities."

Multiple extensions are enabled by logically OR-ing the values that represent the desired extensions.

\fBNotes: Enabling an extension on a CPU that does not support the extension will result in a SIGILL crash. On AIX, all vector instructions can be disabled with the schedo -ro allow_vmx=0 command. DO NOT USE THIS COMMAND to disable vector instructions in the OS when it is running on a CPU level that supports the instructions without also disabling them in libcrpto via the OPENSSL_ppccap environment variable or the application will crash with a SIGILL.

Currently, the following extensions are defined:

Item "0x01" Name: PPC_FPU64 .Sp This flag is obsolete. Item "0x02" Name: PPC_ALTIVEC .Sp Meaning: Use AltiVec (aka VMX) instructions. In some but not all cases, this capability gates the use of later ISA vector instructions. The associated probe instruction is vor (vector logical or). .Sp Effect: Enables use of vector instructions but does not enable extensions added at specific ISA levels. However, disabling this capability disables a subset of vector extensions added at specific ISA levels even if they are otherwise enabled. Item "0x04" Name: PPC_CRYPTO207 .Sp Meaning: Use instructions added in ISA level 2.07. The associated probe instruction instruction is vcipher (vector AES cipher round). .Sp Effect: Enables AES, SHA-2 sigma, and other ISA 2.07 instructions for AES, SHA-2, GHASH, and Poly1305. Item "0x08" Name: PPC_FPU .Sp Meaning: Use FPU instructions. The associated probe instruction is fmr (floating move register). .Sp Effect: Enables Poly1305 FPU implementation. The PPC_CRYPTO207 capability overrides this effect. Item "0x10" Name: PPC_MADD300 .Sp Meaning: Use instructions added in ISA level 3.00. The associated probe instruction is maddhdu (multiply-add high doubleword unsigned). .Sp Effect: Enables use of the polynomial multiply and other ISA 3.00 instructions for AES-GCM, P-384, and P-521. Item "0x20" Name: PPC_MFTB .Sp Meaning: Use the mftb (move from time base) instruction. The associated probe instruction is mftb. .Sp Effect: Enables use of the mftb instruction to sample the lower 32 bits of the CPU time base register in order to acquire entropy. Considered obsolete. The PPC_MFSPR268 capability overrides this capability. Item "0x40" Name: PPC_MFSPR268 .Sp Meaning: Use the mfspr (move from special purpose register) instruction to read SPR 268. The associated probe instruction is mfspr 268. .Sp Effect: Enables use of the mfspr instruction to sample the lower 32 bits of the CPU time base register from SPR 268, the TBL (time base lower) register, in order to acquire entropy. Item "0x80" Name: PPC_BRD31 .Sp Meaning: Use instructions added in ISA level 3.1. The associated probe instruction is brd (byte-reverse doubleword). .Sp Effect: Enables use of ISA 3.1 instructions in ChaCha20. Header "RETURN VALUES" Not available. Header "EXAMPLES" Check currently detected capabilities:

.Vb 2 $ openssl info -cpusettings OPENSSL_ppccap=0x2E .Ve

The detected capabilities in the above example indicate that PPC_MFTB, PPC_FPU, PPC_CRYPTO207, PPC_MFSPR268, and PPC_ALTIVEC are enabled.

Disable all instruction set extensions:

.Vb 1 OPENSSL_ppccap=0x00 .Ve

Enable base AltiVec extensions:

.Vb 1 OPENSSL_ppccap=0x02 .Ve

Header "COPYRIGHT" Copyright 2025 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at <https://www.openssl.org/source/license.html>.