aboutsummaryrefslogtreecommitdiff
path: root/cmake/tuklib_integer.cmake
diff options
context:
space:
mode:
authorLasse Collin <lasse.collin@tukaani.org>2023-03-17 08:41:36 +0200
committerJia Tan <jiat0218@gmail.com>2023-03-17 20:19:29 +0800
commit4523a5ee29f45c0256af67a15771bc8bbd25ba53 (patch)
tree63b8bcb72646bb5c7eb2d2c476aaa6647184fa24 /cmake/tuklib_integer.cmake
parentTests: Update .gitignore. (diff)
downloadxz-4523a5ee29f45c0256af67a15771bc8bbd25ba53.tar.xz
Build: Update comments about unaligned access to mention 64-bit.
Diffstat (limited to 'cmake/tuklib_integer.cmake')
-rw-r--r--cmake/tuklib_integer.cmake7
1 files changed, 3 insertions, 4 deletions
diff --git a/cmake/tuklib_integer.cmake b/cmake/tuklib_integer.cmake
index d7e2e28c..949d2d9f 100644
--- a/cmake/tuklib_integer.cmake
+++ b/cmake/tuklib_integer.cmake
@@ -59,9 +59,8 @@ function(tuklib_integer TARGET_OR_ALL)
endif()
endif()
- # 16-bit and 32-bit unaligned access is fast on x86(-64),
- # big endian PowerPC, and usually on 32/64-bit ARM too.
- # There are others too and ARM could be a false match.
+ # Unaligned access is fast on x86(-64), big endian PowerPC, and usually on
+ # 32/64-bit ARM too. There are others too and ARM could be a false match.
#
# Guess the default value for the option.
# CMake's ability to give info about the target arch seems bad.
@@ -81,7 +80,7 @@ function(tuklib_integer TARGET_OR_ALL)
endif()
option(TUKLIB_FAST_UNALIGNED_ACCESS
"Enable if the system supports *fast* unaligned memory access \
-with 16-bit and 32-bit integers."
+with 16-bit, 32-bit, and 64-bit integers."
"${FAST_UNALIGNED_GUESS}")
tuklib_add_definition_if("${TARGET_OR_ALL}" TUKLIB_FAST_UNALIGNED_ACCESS)