llvm-project/llvm/test/Assembler/invalid-dicompileunit-null-...

; RUN: not llvm-as < %s -disable-output 2>&1 | FileCheck %s

; CHECK: <stdin>:[[@LINE+1]]:36: error: 'file' cannot be null
!0 = distinct !DICompileUnit(file: null)
Verifier: Move checks over from DIDescriptor::Verify() Move over some more checks from `DIDescriptor::Verify()`, and change `LLParser` to require non-null `file:` fields in compile units. I've ignored the comment in test/Assembler/metadata-null-operands.ll since I disagree with it. At the time that test was written (r229960), the debug info verifier wasn't on by default, so my comment there is in the context of not expecting the verifier to be useful. It is now, and besides that, since r233394 we can check when parsing textual IR whether an operand is null that shouldn't be. llvm-svn: 233654 2015-03-31 08:47:15 +08:00			`; RUN: not llvm-as < %s -disable-output 2>&1 \| FileCheck %s`

DI: Disallow uniquable DICompileUnits Since r241097, `DIBuilder` has only created distinct `DICompileUnit`s. The backend is liable to start relying on that (if it hasn't already), so make uniquable `DICompileUnit`s illegal and automatically upgrade old bitcode. This is a nice cleanup, since we can remove an unnecessary `DenseSet` (and the associated uniquing info) from `LLVMContextImpl`. Almost all the testcases were updated with this script: git grep -e '= !DICompileUnit' -l -- test \| grep -v test/Bitcode \| xargs sed -i '' -e 's,= !DICompileUnit,= distinct !DICompileUnit,' I imagine something similar should work for out-of-tree testcases. llvm-svn: 243885 2015-08-04 01:26:41 +08:00			`; CHECK: <stdin>:[[@LINE+1]]:36: error: 'file' cannot be null`
			`!0 = distinct !DICompileUnit(file: null)`