LLVM build failure at head on CI after integrate #2537
Description
This is also happening on my local machine - after the last integrate, i'm getting the build failure: 05e243d
ERROR: /home/runner/.cache/bazel/_bazel_runner/0a8e1561e62ae8be6f076ff617869391/external/+_repo_rules+llvm-project/llvm/BUILD.bazel:225:11: Compiling llvm/lib/Support/APFloat.cpp failed: (Exit 1): clang failed: error executing CppCompile command (from target @@+_repo_rules+llvm-project//llvm:Support) /usr/lib/llvm-19/bin/clang -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -Wunused-but-set-parameter -Wno-free-nonheap-object -fcolor-diagnostics -fno-omit-frame-pointer -g0 ... (remaining 101 arguments skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
In file included from external/+_repo_rules+llvm-project/llvm/lib/Support/APFloat.cpp:14:
In file included from external/+_repo_rules+llvm-project/llvm/include/llvm/ADT/APFloat.h:19:
In file included from external/+_repo_rules+llvm-project/llvm/include/llvm/ADT/ArrayRef.h:13:
external/+_repo_rules+llvm-project/llvm/include/llvm/ADT/STLExtras.h:2164:10: error: call to 'bind_front' is ambiguous
2164 | return bind_front(std::equal_to<>{}, std::forward<T>(Arg));
| ^~~~~~~~~~
external/+_repo_rules+llvm-project/llvm/lib/Support/APFloat.cpp:3949:59: note: in instantiation of function template specialization 'llvm::equal_to<int>' requested here
3949 | bool all_zero_significand = llvm::all_of(mysignificand, equal_to(0));
| ^
external/+_repo_rules+llvm-project/llvm/include/llvm/ADT/STLForwardCompat.h:270:16: note: candidate function [with FnT = std::equal_to<void>, BindArgsT = <int>]
270 | constexpr auto bind_front(FnT &&Fn, // NOLINT(readability-identifier-naming)
| ^
/usr/lib/gcc/x86_64-linux-gnu/14/../../../../include/c++/14/functional:1041:5: note: candidate function [with _Fn = std::equal_to<void>, _Args = <int>]
1041 | bind_front(_Fn&& __fn, _Args&&... __args)
| ^
1 error generated.
Analyzing: 2527 targets (931 packages loaded, 62929 targets configured)
[7,951 / 20,233] checking cached actions
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 117.732s, Critical Path: 23.06s
INFO: 4131 processes: 3829 action cache hit, 3217 internal, 914 processwrapper-sandbox.
ERROR: Build did NOT complete successfully
FAILED:
Error: Process completed with exit code 1.