diff options
author | Kees Cook <kees@kernel.org> | 2025-08-04 09:44:11 -0700 |
---|---|---|
committer | Kees Cook <kees@kernel.org> | 2025-09-08 14:58:52 -0700 |
commit | 945fc9dbd8377e48246de3a5f0104ebe82399eb0 (patch) | |
tree | 61d9de59c334269e7838907b1f2781176cb6a698 /lib/mpi/mpi-mod.c | |
parent | b77fee88bfdfcba2f92c9de2ed1af793c96c46d8 (diff) |
xtensa: Add __attribute_const__ to ffs()-family implementations
While tracking down a problem where constant expressions used by
BUILD_BUG_ON() suddenly stopped working[1], we found that an added static
initializer was convincing the compiler that it couldn't track the state
of the prior statically initialized value. Tracing this down found that
ffs() was used in the initializer macro, but since it wasn't marked with
__attribute__const__, the compiler had to assume the function might
change variable states as a side-effect (which is not true for ffs(),
which provides deterministic math results).
Add missing __attribute_const__ annotations to Xtensa's implementations
of ffs(), __ffs(), fls(), __fls(), ffz() functions. These are pure
mathematical functions that always return the same result for the
same input with no side effects, making them eligible for compiler
optimization.
Build tested ARCH=xtensa defconfig with GCC xtensa-linux 15.1.0.
Link: https://github.com/KSPP/linux/issues/364 [1]
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lore.kernel.org/r/20250804164417.1612371-15-kees@kernel.org
Signed-off-by: Kees Cook <kees@kernel.org>
Diffstat (limited to 'lib/mpi/mpi-mod.c')
0 files changed, 0 insertions, 0 deletions