diff options
author | Kevin Gleason <gleasonk@google.com> | 2023-07-24 20:39:40 -0700 |
---|---|---|
committer | Jacques Pienaar <jpienaar@google.com> | 2023-07-24 20:45:43 -0700 |
commit | 998003eaf7b91b5620eeb0b77c81654b9f36efb7 (patch) | |
tree | 7f5b2fd7b398479a6323bc972ddb8a6e219d2ab6 /llvm/lib/Analysis/ModuleSummaryAnalysis.cpp | |
parent | dd84f5f91c6b234a2f188b6acf8557cae81b8a53 (diff) | |
download | llvm-998003eaf7b91b5620eeb0b77c81654b9f36efb7.zip llvm-998003eaf7b91b5620eeb0b77c81654b9f36efb7.tar.gz llvm-998003eaf7b91b5620eeb0b77c81654b9f36efb7.tar.bz2 |
[mlir] Fix for MSVC bool splat issue encountered.
When building MLIR using bazel on windows with MSVC2019, bool splats
were being created incorrectly:
```
dense<[true,true,true,true]> : tensor<4xi1>
-(parse with mlir-opt)-> dense<[true, false, false, false]> : tensor<4xi1>
```
Appears that a Windows bazel build produces a corrupt DenseIntOrFPElementsAttr.
Unable to repro using MSVC and cmake.
Issue first discovered here:
https://github.com/google/jax/issues/16394
Added test point for reproduction:
```
$ bazel test @llvm-project//mlir/unittests:ir_tests --test_arg=--gtest_filter=DenseSplatTest.BoolSplatSmall
```
Differential Revision: https://reviews.llvm.org/D155745
Diffstat (limited to 'llvm/lib/Analysis/ModuleSummaryAnalysis.cpp')
0 files changed, 0 insertions, 0 deletions