llvm-project.git/llvm/test/Transforms/InferAddressSpaces/AMDGPU/insert-pos-assert.ll, branch users/nico/python-2

InferAddressSpaces: Replace undef with poison in tests (#130083)

2025-03-06T16:20:46+00:00

[Transforms] Convert tests to opaque pointers (NFC)

2024-02-05T10:57:34+00:00

InferAddressSpaces: Switch tests to use opt -passes

2022-11-28T01:26:16+00:00

InferAddressSpaces: Convert tests to opaque pointers

2022-11-28T01:26:16+00:00

Had constantexprs be mangled by the opaquify script; had to update
those lines manually:
  NVPTX/bug31948.ll
  AMDGPU/old-pass-regressions.ll
  AMDGPU/old-pass-regressions-inseltpoison.ll
  AMDGPU/infer-address-space.ll

Required re-reunning update_test_checks:
  AMDGPU/redundant-addrspacecast.ll

In AMDGPU/insert-pos-assert.ll, bitcast_insert_pos_assert_2 deleted a
getelementptr of 0 which I'm guessing was relevant. Replaced with an
offset 1 GEP to ensure another addrspacecast is inserted.

AMDGPU/infer-getelementptr.ll had one case improve by introducing an
inbounds.

[InferAddressSpaces] Fix assert on invalid bitcast placement

2022-04-08T03:07:53+00:00

Similar to the problem in 0bb25b4603, bitcasts that are inserted must
dominate all uses. When rewriting "values" with "new values" that have
the updated address space, we may replace the "new value" with a bitcast
if one of the original users is an addresspace cast. This bitcast must
be inserted before ALL users, not only before the addresspace cast.

Reviewed By: arsenm

Differential Revision: https://reviews.llvm.org/D122964

[InferAddressSpaces] Fix assert on invalid cast ordering

2022-02-11T18:02:30+00:00

If a cast is needed when replacing uses with newly created values, the
cast must be inserted after the instruction that defines the new value.

Fixes: SWDEV-321215

Reviewed By: arsenm

Differential Revision: https://reviews.llvm.org/D119524