en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/AMDGPU/GlobalISel/buffer-schedule.ll#59f68652 [AMDGPU][GISel] Fix MMO for raw/struct buffer access with non-constant offsetCodegen for the raw/struct buffer access intrinsics would update theoffset in the MMO to reflect the combined offset, if it was known to beconstant. If the combined offset was not known to be constant, or ifthere was an index, it would set the offset in the MMO to 0. This isunsafe because it makes it look like the access does not alias withanother access with a fixed non-zero offset.Fix these cases by setting the pointer in the MMO to null, to reflectthe fact that we do not have any known IR value pointer + constantoffset for the access.D106284 did this for SelectionDAG. This is the corresponding fix forGlobalISel.Differential Revision: https://reviews.llvm.org/D106451 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/AMDGPU/GlobalISel/buffer-schedule.ll Wed, 21 Jul 2021 14:53:59 +0000 Jay Foad <jay.foad@amd.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/AMDGPU/GlobalISel/buffer-schedule.ll#683b9ed0 [AMDGPU] Pre-commit global-isel test case for D106451This test case shows the scheduler wrongly reordering two bufferaccesses that might alias. List of files: /llvm-project-15.0.7/llvm/test/CodeGen/AMDGPU/GlobalISel/buffer-schedule.ll Wed, 21 Jul 2021 10:29:04 +0000 Jay Foad <jay.foad@amd.com>