llvm/test/Bitcode/identification.ll

; Check that a block "IDENTIFICATION_BLOCK_ID" is emitted.
;RUN: llvm-as < %s | llvm-bcanalyzer -dump | FileCheck %s
;CHECK: <IDENTIFICATION_BLOCK_ID
;CHECK-NEXT: <STRING
;CHECK-NEXT: <EPOCH
;CHECK-NEXT: </IDENTIFICATION_BLOCK_ID
Add an (optional) identification block in the bitcode Processing bitcode from a different LLVM version can lead to unexpected behavior. The LLVM project guarantees autoupdating bitcode from a previous minor revision for the same major, but can't make any promise when reading bitcode generated from a either a non-released LLVM, a vendor toolchain, or a "future" LLVM release. This patch aims at being more user-friendly and allows a bitcode produce to emit an optional block at the beginning of the bitcode that will contains an opaque string intended to describe the bitcode producer information. The bitcode reader will dump this information alongside any error it reports. The optional block also includes an "epoch" number, monotonically increasing when incompatible changes are made to the bitcode. The reader will reject bitcode whose epoch is different from the one expected. Differential Revision: http://reviews.llvm.org/D13666 From: Mehdi Amini <mehdi.amini@apple.com> git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@251325 91177308-0d34-0410-b5e6-96231b3b80d8 2015-10-26 18:37:00 +00:00			`; Check that a block "IDENTIFICATION_BLOCK_ID" is emitted.`
			`;RUN: llvm-as < %s \| llvm-bcanalyzer -dump \| FileCheck %s`
			`;CHECK: <IDENTIFICATION_BLOCK_ID`
			`;CHECK-NEXT: <STRING`
			`;CHECK-NEXT: <EPOCH`
			`;CHECK-NEXT: </IDENTIFICATION_BLOCK_ID`