summaryrefslogtreecommitdiff
path: root/scripts/generate_rust_analyzer.py
diff options
context:
space:
mode:
authorJohn Hubbard <jhubbard@nvidia.com>2024-05-03 06:51:02 +0300
committerTejun Heo <tj@kernel.org>2024-05-03 22:06:09 +0300
commit1da2363228d68da266443e7a85fa91edc2be3dac (patch)
treed903bf92b6d2e321f782c2d4f706ffeec2b507a5 /scripts/generate_rust_analyzer.py
parentb7d56d953a67c839a514e382596d5af29b8d6d87 (diff)
downloadlinux-1da2363228d68da266443e7a85fa91edc2be3dac.tar.xz
selftests/cgroup: fix clang build failures for abs() calls
First of all, in order to build with clang at all, one must first apply Valentin Obst's build fix for LLVM [1]. Once that is done, then when building with clang, via: make LLVM=1 -C tools/testing/selftests ...clang is pickier than gcc, about which version of abs(3) to call, depending on the argument type: int abs(int j); long labs(long j); long long llabs(long long j); ...and this is causing both build failures and warnings, when running: make LLVM=1 -C tools/testing/selftests Fix this by calling labs() in value_close(), because the arguments are unambiguously "long" type. [1] https://lore.kernel.org/all/20240329-selftests-libmk-llvm-rfc-v1-1-2f9ed7d1c49f@valentinobst.de/ Signed-off-by: John Hubbard <jhubbard@nvidia.com> Reviewed-by: Roman Gushchin <roman.gushchin@linux.dev> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions