summaryrefslogtreecommitdiffstats
path: root/llvm/test/Bitcode/upgrade-module-flag.ll
diff options
context:
space:
mode:
authorMehdi Amini <mehdi.amini@apple.com>2016-09-16 00:38:18 +0000
committerMehdi Amini <mehdi.amini@apple.com>2016-09-16 00:38:18 +0000
commitb53b62eb69cd5768423786c5ced700bc2d1d2e20 (patch)
treecd0b7f050e0efcf5c203a86dc9be0e4ffd253f38 /llvm/test/Bitcode/upgrade-module-flag.ll
parent1fbaf535d6a4555a751d1285889a7a1f52dfafc5 (diff)
downloadbcm5719-llvm-b53b62eb69cd5768423786c5ced700bc2d1d2e20.tar.gz
bcm5719-llvm-b53b62eb69cd5768423786c5ced700bc2d1d2e20.zip
Fix autoupgrade logic for Objective-C class properties module flag
Previous we were issuing an error when linking a module containing the new Objective-C metadata structure for class properties with an "old" one. Now instead we downgrade the module flag so that the Objective-C runtime does not expect the new metadata structure. This is consistent with what ld64 is doing on binary files. Differential Revision: https://reviews.llvm.org/D24620 llvm-svn: 281685
Diffstat (limited to 'llvm/test/Bitcode/upgrade-module-flag.ll')
-rw-r--r--llvm/test/Bitcode/upgrade-module-flag.ll2
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/test/Bitcode/upgrade-module-flag.ll b/llvm/test/Bitcode/upgrade-module-flag.ll
index fe52a3298e4..d6741faa837 100644
--- a/llvm/test/Bitcode/upgrade-module-flag.ll
+++ b/llvm/test/Bitcode/upgrade-module-flag.ll
@@ -6,4 +6,4 @@
!0 = !{i32 1, !"Objective-C Image Info Version", i32 0}
; CHECK: !0 = !{i32 1, !"Objective-C Image Info Version", i32 0}
-; CHECK: !1 = !{i32 1, !"Objective-C Class Properties", i32 0}
+; CHECK: !1 = !{i32 4, !"Objective-C Class Properties", i32 0}
OpenPOWER on IntegriCloud