mirrors/llvm-project
0
0
Fork 0
mirror of https://github.com/llvm/llvm-project.git synced 2025-04-28 10:46:07 +00:00
Code Issues Projects Releases Wiki Activity
llvm-project/llvm/test/tools/llvm-reduce/reduce-module-flags.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

40 lines
1.5 KiB
LLVM
Raw Normal View History

llvm-reduce: Reduce individual operands of named metadata The current reduction tries all or nothing elimination of named metadata. I noticed in one case where one of the module flags was necessary, but it left the rest. Reduce the individual operands of named metadata nodes that are known to behave like lists. Be conservative since some named metadata may have more specific verifier requirements for the operands.
2023-01-01 10:52:02 -05:00
; Test keeping one module flag
; RUN: llvm-reduce --abort-on-invalid-reduction --delta-passes=named-metadata --test=FileCheck --test-arg=--check-prefix=CHECK-INTERESTINGNESS0 --test-arg=%s --test-arg=--input-file %s -o %t.0
; RUN: FileCheck --check-prefix=RESULT0 %s < %t.0
; Test keeping two module flags
; RUN: llvm-reduce --abort-on-invalid-reduction --delta-passes=named-metadata --test=FileCheck --test-arg=--check-prefix=CHECK-INTERESTINGNESS1 --test-arg=%s --test-arg=--input-file %s -o %t.1
; RUN: FileCheck --check-prefix=RESULT1 %s < %t.1
; Test removing all module flags
; RUN: llvm-reduce --abort-on-invalid-reduction --delta-passes=named-metadata --test=FileCheck --test-arg=--check-prefix=CHECK-INTERESTINGNESS2 --test-arg=%s --test-arg=--input-file %s -o %t.2
; RUN: FileCheck --check-prefix=RESULT2 %s < %t.2
; CHECK-INTERESTINGNESS0: "openmp-device"
; CHECK-INTERESTINGNESS1: "wchar_size"
; CHECK-INTERESTINGNESS1: "openmp"
; CHECK-INTERESTINGNESS2: !llvm.module.flags
; RESULT0: !llvm.module.flags = !{!0}
; RESULT0: !0 = !{i32 7, !"openmp-device", i32 50}
; RESULT1: !llvm.module.flags = !{!0, !1}
; RESULT1: !0 = !{i32 1, !"wchar_size", i32 4}
; RESULT1: !1 = !{i32 7, !"openmp", i32 50}
; RESULT2: !llvm.module.flags = !{}
[LTO][GlobalDCE] Use pass parameter instead of module flag for LTO phase D63932 added a module flag to indicate that we are executing the regular LTO post merge pipeline, so that GlobalDCE could perform more aggressive optimization for Dead Virtual Function Elimination. This caused issues trying to reuse bitcode that had already been through the LTO pipeline (see context in D139816). Instead support this by passing down a parameter flag to the GlobalDCEPass constructor, which is the more usual way for indicating this information. Most test changes are to remove incidental uses of this flag. Of the 2 real uses, llvm/test/LTO/ARM/lto-linking-metadata.ll is now obsolete and removed in this patch, and the virtual-functions-visibility-post-lto.ll test is updated to use the regular LTO default pipeline where this parameter is set to true. Differential Revision: https://reviews.llvm.org/D153655
2023-06-23 11:01:22 -07:00
!llvm.module.flags = !{!0, !1, !2, !3, !4}
llvm-reduce: Reduce individual operands of named metadata The current reduction tries all or nothing elimination of named metadata. I noticed in one case where one of the module flags was necessary, but it left the rest. Reduce the individual operands of named metadata nodes that are known to behave like lists. Be conservative since some named metadata may have more specific verifier requirements for the operands.
2023-01-01 10:52:02 -05:00
[AMDGPU] Rename COV module flag to amdhsa_code_object_version (#79905) The previous name 'amdgpu_code_object_version', was misleading since this is really a property of the HSA OS. The new spelling also matches the asm directive I added in bc82cfb.
2024-03-06 09:51:48 -05:00
!0 = !{i32 1, !"amdhsa_code_object_version", i32 400}
llvm-reduce: Reduce individual operands of named metadata The current reduction tries all or nothing elimination of named metadata. I noticed in one case where one of the module flags was necessary, but it left the rest. Reduce the individual operands of named metadata nodes that are known to behave like lists. Be conservative since some named metadata may have more specific verifier requirements for the operands.
2023-01-01 10:52:02 -05:00
!1 = !{i32 1, !"wchar_size", i32 4}
!2 = !{i32 7, !"openmp", i32 50}
!3 = !{i32 7, !"openmp-device", i32 50}
!4 = !{i32 8, !"PIC Level", i32 1}
Reference in New Issue Copy Permalink