llvm-mirror/test/Bitcode/thinlto-summary-globalvar.ll

; RUN: opt -module-summary %s -o - | llvm-bcanalyzer -dump | FileCheck %s
; Check with new pass manager (by enabling a random pass in the new pipeline).
; RUN: opt -passes=gvn -module-summary %s -o - | llvm-bcanalyzer -dump | FileCheck %s

; CHECK: <GLOBALVAL_SUMMARY_BLOCK

@a = global i32 0
BitcodeWriter: Remove redundant (and incorrect) check for whether to emit module summary. The function name Module::empty() is slightly misleading in that it only tests for the presence of functions in the module. However we still want to emit the module summary if the module contains only global variables or aliases. The presence of such entities can be determined simply by checking the summary directly, as we are doing below. Differential Revision: http://reviews.llvm.org/D21669 llvm-svn: 273638 2016-06-24 03:58:02 +02:00			`; RUN: opt -module-summary %s -o - \| llvm-bcanalyzer -dump \| FileCheck %s`
[PM] Port ModuleSummaryIndex analysis to new pass manager Summary: Port the ModuleSummaryAnalysisWrapperPass to the new pass manager. Use it in the ported BitcodeWriterPass (similar to how we use the legacy ModuleSummaryAnalysisWrapperPass in the legacy WriteBitcodePass). Also, pass the -module-summary opt flag through to the new pass manager pipeline and through to the bitcode writer pass, and add a test that uses it. Reviewers: mehdi_amini Subscribers: llvm-commits, mehdi_amini Differential Revision: https://reviews.llvm.org/D23439 llvm-svn: 278508 2016-08-12 15:53:02 +02:00			`; Check with new pass manager (by enabling a random pass in the new pipeline).`
			`; RUN: opt -passes=gvn -module-summary %s -o - \| llvm-bcanalyzer -dump \| FileCheck %s`
BitcodeWriter: Remove redundant (and incorrect) check for whether to emit module summary. The function name Module::empty() is slightly misleading in that it only tests for the presence of functions in the module. However we still want to emit the module summary if the module contains only global variables or aliases. The presence of such entities can be determined simply by checking the summary directly, as we are doing below. Differential Revision: http://reviews.llvm.org/D21669 llvm-svn: 273638 2016-06-24 03:58:02 +02:00
			`; CHECK: <GLOBALVAL_SUMMARY_BLOCK`

			`@a = global i32 0`