================
@@ -1,7 +1,7 @@
 ; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py 
UTC_ARGS: --version 2
 ; RUN: llc -amdgpu-scalarize-global-loads=false -mtriple=amdgpu6.00 < %s | 
FileCheck -check-prefixes=SI %s
 ; RUN: llc -amdgpu-scalarize-global-loads=false -mtriple=amdgpu8.03 
-mattr=-flat-for-global < %s | FileCheck -check-prefixes=VI %s
-; RUN: llc -amdgpu-scalarize-global-loads=false -mtriple=amdgpu11.00 
-mattr=+real-true16,-flat-for-global < %s | FileCheck -check-prefixes=GFX11 %s
+; RUN: llc -amdgpu-scalarize-global-loads=false -mtriple=amdgpu11.00 
-mattr=+real-true16,-flat-for-global < %s | FileCheck 
-check-prefixes=GFX11-TRUE16 %s
 ; RUN: llc -amdgpu-scalarize-global-loads=false -mtriple=amdgpu11.00 
-mattr=-real-true16,-flat-for-global < %s | FileCheck 
-check-prefixes=GFX11-FAKE16 %s
----------------
kosarev wrote:

Using GFX11 along with GFX11-FAKE16 looks a bit like a new convention, but on 
the other hand, in such cases that would be a change only to change it back 
later, so doesn't make much sense. I think the downstream could be updated to 
match instead.

https://github.com/llvm/llvm-project/pull/209889
_______________________________________________
llvm-branch-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

Reply via email to