aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Reader/BitcodeReader.cpp
diff options
context:
space:
mode:
authorMoritz Zielke <moritz.zielke@gmail.com>2025-11-06 00:26:22 +0100
committerGitHub <noreply@github.com>2025-11-05 23:26:22 +0000
commit46c948935dd94c8caa0e8e850a8ec95dff784bd2 (patch)
tree6787a360fc938928904d2d007efea3603d88c648 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp
parent1ff0098f7c9d3d5f77aaf10ed995964746f35b88 (diff)
downloadllvm-46c948935dd94c8caa0e8e850a8ec95dff784bd2.zip
llvm-46c948935dd94c8caa0e8e850a8ec95dff784bd2.tar.gz
llvm-46c948935dd94c8caa0e8e850a8ec95dff784bd2.tar.bz2
[GlobalISel] Add `G_EXTRACT_VECTOR_ELT` for `computeKnownBits` (#164825)
The code is ported from `SelectionDAG::computeKnownBits`. As a result of adding `G_EXTRACT_VECTOR_ELT` to `GlobalISel`, the code generated for some of the existing regression tests changes. The changes in `neon-extadd-extract.ll` and `knownbits-buildvector.mir` look good to me. Though I'm struggling to understand the diff in `sdiv.i64.ll`. Is there a test that checks if the generated amdgcn produces the correct result? Or tools that help with executing it (I do have an AMD GPU)? **Edit**: Related to #150515
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions