USE Flag: cet

Provenance Summary

Authoritative Scope: package_scoped | Distinct Packages: 9 | Repository Package Instances: 9

Search

Manage

Package-Scoped Descriptions (use.local.desc / metadata.xml)

Package Source Kind Source File Description
dev-debug/gdb metadata.xml dev-debug/gdb/metadata.xml Enable Intel Control-flow Enforcement Technology.
dev-debug/gdb use.local.desc profiles/use.local.desc Enable Intel Control-flow Enforcement Technology.
llvm-core/clang-common metadata.xml llvm-core/clang-common/metadata.xml Enable support for control flow hijacking protection. On amd64, this provides Intel Control Flow Enforcement Technology (CET). Only provides benefits on newer CPUs. For Intel, the CPU must be at least as new as Tiger Lake. For AMD, it must be at least as new as Zen 3. This is harmless on older CPUs, but provides no benefit either.
llvm-core/clang-common use.local.desc profiles/use.local.desc Enable support for control flow hijacking protection. On amd64, this provides Intel Control Flow Enforcement Technology (CET). Only provides benefits on newer CPUs. For Intel, the CPU must be at least as new as Tiger Lake. For AMD, it must be at least as new as Zen 3. This is harmless on older CPUs, but provides no benefit either.
llvm-runtimes/libunwind metadata.xml llvm-runtimes/libunwind/metadata.xml Enable Intel Control-flow Enforcement Technology
llvm-runtimes/libunwind use.local.desc profiles/use.local.desc Enable Intel Control-flow Enforcement Technology
media-libs/x265 metadata.xml media-libs/x265/metadata.xml Enable Intel Control-flow Enforcement Technology.
media-libs/x265 use.local.desc profiles/use.local.desc Enable Intel Control-flow Enforcement Technology.
sys-devel/binutils metadata.xml sys-devel/binutils/metadata.xml Enable Intel Control-flow Enforcement Technology.
sys-devel/binutils use.local.desc profiles/use.local.desc Enable Intel Control-flow Enforcement Technology.
sys-devel/binutils-hppa64 metadata.xml sys-devel/binutils-hppa64/metadata.xml Enable Intel Control-flow Enforcement Technology.
sys-devel/binutils-hppa64 use.local.desc profiles/use.local.desc Enable Intel Control-flow Enforcement Technology.
sys-devel/gcc metadata.xml sys-devel/gcc/metadata.xml Enable support for control flow hijacking protection. On amd64, this provides Intel Control Flow Enforcement Technology (CET). On arm64, this provides Branch Target Identification (BTI) and Pointer Authentication Code (PAC) support. This is only effective on amd64 or arm64. Only provides benefits on newer CPUs. For Intel, the CPU must be at least as new as Tiger Lake. For AMD, it must be at least as new as Zen 3. This is harmless on older CPUs, but provides no benefit either. For ARM64, PAC was introduced in armv8.3-a, and BTI was introduced in armv8.5-a. When combined with USE=hardened on amd64, GCC will set -fcf-protection by default when building software. The effect is minimal on systems which do not support it, other than a possible small increase in codesize for the NOPs. The generated code is therefore compatible with i686 at the earliest. On arm64, GCC will set -mbranch-protection=standard by default when building software.
sys-devel/gcc use.local.desc profiles/use.local.desc Enable support for control flow hijacking protection. On amd64, this provides Intel Control Flow Enforcement Technology (CET). On arm64, this provides Branch Target Identification (BTI) and Pointer Authentication Code (PAC) support. This is only effective on amd64 or arm64. Only provides benefits on newer CPUs. For Intel, the CPU must be at least as new as Tiger Lake. For AMD, it must be at least as new as Zen 3. This is harmless on older CPUs, but provides no benefit either. For ARM64, PAC was introduced in armv8.3-a, and BTI was introduced in armv8.5-a. When combined with USE=hardened on amd64, GCC will set -fcf-protection by default when building software. The effect is minimal on systems which do not support it, other than a possible small increase in codesize for the NOPs. The generated code is therefore compatible with i686 at the earliest. On arm64, GCC will set -mbranch-protection=standard by default when building software.
sys-libs/binutils-libs metadata.xml sys-libs/binutils-libs/metadata.xml Enable Intel Control-flow Enforcement Technology.
sys-libs/binutils-libs use.local.desc profiles/use.local.desc Enable Intel Control-flow Enforcement Technology.
sys-libs/glibc metadata.xml sys-libs/glibc/metadata.xml Enable Intel Control-flow Enforcement Technology (needs binutils 2.29 and gcc 8)
sys-libs/glibc use.local.desc profiles/use.local.desc Enable Intel Control-flow Enforcement Technology (needs binutils 2.29 and gcc 8)

Package Usage Occurrences

Package Observations Versions Local Description (use.local.desc) Metadata Description (metadata.xml)
dev-debug/gdb IUSE 16.3, 17.1, 17.2, 18.1, 9999 Enable Intel Control-flow Enforcement Technology. Enable Intel Control-flow Enforcement Technology.
llvm-core/clang-common IUSE 20.1.8, 21.1.8, 22.1.8, 23.1.6, 24.0.0.9999, 24.0.0_pre20261115, 24.0.0_pre20261121 Enable support for control flow hijacking protection. On amd64, this provides Intel Control Flow Enforcement Technology (CET). Only provides benefits on newer CPUs. For Intel, the CPU must be at least as new as Tiger Lake. For AMD, it must be at least as new as Zen 3. This is harmless on older CPUs, but provides no benefit either. Enable support for control flow hijacking protection. On amd64, this provides Intel Control Flow Enforcement Technology (CET). Only provides benefits on newer CPUs. For Intel, the CPU must be at least as new as Tiger Lake. For AMD, it must be at least as new as Zen 3. This is harmless on older CPUs, but provides no benefit either.
llvm-runtimes/libunwind IUSE 22.1.8, 23.1.6, 24.0.0.9999, 24.0.0_pre20261115, 24.0.0_pre20261121 Enable Intel Control-flow Enforcement Technology Enable Intel Control-flow Enforcement Technology
media-libs/x265 IUSE 4.3, 9999 Enable Intel Control-flow Enforcement Technology. Enable Intel Control-flow Enforcement Technology.
sys-devel/binutils IUSE 2.35.2, 2.36.1, 2.37_p1, 2.38, 2.39, 2.40, 2.41, 2.42, 2.43, 2.44, 2.45, 2.45.1, 2.46.0, 2.46.1, 2.47, 2.47.9999, 9999 Enable Intel Control-flow Enforcement Technology. Enable Intel Control-flow Enforcement Technology.
sys-devel/binutils-hppa64 IUSE 2.37_p1, 2.38, 2.39, 2.40, 2.41, 2.42, 2.43, 2.44, 2.45, 2.45.1, 2.46.0, 2.46.1, 2.47, 9999 Enable Intel Control-flow Enforcement Technology. Enable Intel Control-flow Enforcement Technology.
sys-devel/gcc metadata only - Enable support for control flow hijacking protection. On amd64, this provides Intel Control Flow Enforcement Technology (CET). On arm64, this provides Branch Target Identification (BTI) and Pointer Authentication Code (PAC) support. This is only effective on amd64 or arm64. Only provides benefits on newer CPUs. For Intel, the CPU must be at least as new as Tiger Lake. For AMD, it must be at least as new as Zen 3. This is harmless on older CPUs, but provides no benefit either. For ARM64, PAC was introduced in armv8.3-a, and BTI was introduced in armv8.5-a. When combined with USE=hardened on amd64, GCC will set -fcf-protection by default when building software. The effect is minimal on systems which do not support it, other than a possible small increase in codesize for the NOPs. The generated code is therefore compatible with i686 at the earliest. On arm64, GCC will set -mbranch-protection=standard by default when building software. Enable support for control flow hijacking protection. On amd64, this provides Intel Control Flow Enforcement Technology (CET). On arm64, this provides Branch Target Identification (BTI) and Pointer Authentication Code (PAC) support. This is only effective on amd64 or arm64. Only provides benefits on newer CPUs. For Intel, the CPU must be at least as new as Tiger Lake. For AMD, it must be at least as new as Zen 3. This is harmless on older CPUs, but provides no benefit either. For ARM64, PAC was introduced in armv8.3-a, and BTI was introduced in armv8.5-a. When combined with USE=hardened on amd64, GCC will set -fcf-protection by default when building software. The effect is minimal on systems which do not support it, other than a possible small increase in codesize for the NOPs. The generated code is therefore compatible with i686 at the earliest. On arm64, GCC will set -mbranch-protection=standard by default when building software.
sys-libs/binutils-libs IUSE 2.35.2, 2.36.1, 2.37_p1, 2.38, 2.39, 2.40, 2.41, 2.42, 2.43, 2.44, 2.45, 2.45.1, 2.46.0, 2.46.1, 2.47, 9999 Enable Intel Control-flow Enforcement Technology. Enable Intel Control-flow Enforcement Technology.
sys-libs/glibc IUSE 2.31, 2.32, 2.33, 2.34, 2.35, 2.36, 2.37, 2.38, 2.39, 2.40, 2.41, 2.42, 2.43, 2.43.9999, 2.44, 2.44.9999, 9999 Enable Intel Control-flow Enforcement Technology (needs binutils 2.29 and gcc 8) Enable Intel Control-flow Enforcement Technology (needs binutils 2.29 and gcc 8)