[UpdateTestChecks] Fix %update_mc_test_checks substitution
We need to explicitly pass --llvm-mc-binary to avoid picking up llvm-mc
from somewhere else in $PATH. Noticed this because test lines were being
generated that didn't include my latest changes to update_mc_test_checks.py
Pull Request: https://github.com/llvm/llvm-project/pull/172230
databases/clickhouse-cpp: Add new port
clickhouse-cpp is the official C++ client library for ClickHouse,
providing a fast and type-safe interface to ClickHouse using its
native binary protocol.
[VPlan] Handle BranchOnTwoConds in simplifyBranchCondition.
This fixes a crash after introducing BranchOnTwoConds (524b1788,
https://github.com/llvm/llvm-project/pull/172750) when trying to
replace BranchOnTwoConds with a VPBranchOnCond, without dissolving the
region.
In that case, we need to update the appropriate condition operand.
InstCombine: Introduce nsz flag on minimum/maximum in SimplifyDemandedFPClass
Alive isn't particularly happy with this in the case where
one of the inputs could be zero, but I think
it's wrong: https://alive2.llvm.org/ce/z/dF7V6k
nsz shouldn't permit introducing a -0 result where
there wasn't one in the input here.
[mlir][amdgpu] Fix DMA lowerings. (#174008)
* Fixes off by one error where tensor_dim_0_stride was always set to 1.
* Instead of always setting this value to 1, tensor_dim_0_stride is the
stride across the last dimension.
[flang] Fixed operations hoisting out of fir.do_concurrent. (#173502)
LICM (#173438) may insert new operations at the beginning of
`fir.do_concurrent`'s block and they cannot be always hoisted
to the alloca-block of the parent operation. This patch
only moves `fir.alloca`s into the alloca-block, and moves
all other operations right before fir.do_concurrent.
[MCA] Ignore host -mcpu when target lacks said CPU (#174004)
#173399 failed on buildbot llvm-clang-ubuntu-x-aarch64-pauth. This patch
aims to rectify this.
--------------
llvm-mca rewrites `-mcpu=native` to `sys::getHostCPUName()` and then
immediately instantiates an
`MCSubtargetInfo`. If the build host is x86 but the selected triple is
AArch64, then the CPU string (e.g. “znver4”) isn’t valid, so
`InitMCProcessorInfo` emits a warning. This broke lit tests on cross
compilation.
This patch aims to fix this by creating a default subtarget first,
querying `STI->isCPUStringValid(hostCPU)`
and only recreating the subtarget with the detected host CPU when it’s
supported.
`mcpu-help.test` has been moved into the AArch64 directory, as it is not
target-independent
[HLSL] Add allresourcesbound option to DXC driver and set corresponding module flag (#173411)
This PR adds a new CC1 option and a new dxc driver option. The DXC
option, when set, is translated into the new CC1 option.
The `all-resources-bound` dxc option will create a metadata module flag,
and the print-dx-shader-flags pass will set the appropriate shader
module flag from this metadata module flag.
Fixes https://github.com/llvm/llvm-project/issues/112264
[MLIR][Bufferization]: Handle invalid memref element types (#173692)
Fixes #128329, Fixes #128330, Fixes #173565, Fixes #114730
There is an assertion failure in `-one-shot-bufferize` when tensors that
have an element type that can't be a memref element type are
encountered.
https://github.com/llvm/llvm-project/blob/f8d3f47e1fd09392aa30df83849b25acd8c59a25/mlir/include/mlir/IR/BuiltinTypes.h#L440
We can't emit a to_tensor for ops that do implement
`BufferizableOpInterface`, and i don't think quantizing is the right
move either, so erroring seemed like the best fit.
After some trial and error, `defaultGetBufferType` seems like the most
functional and least invasive place to put this check.
