llvm-project/llvm/test/Linker/drop-debug.ll

; RUN: llvm-link %p/Inputs/drop-debug.bc -o %t 2>&1 | FileCheck %s

;; drop-debug.bc was created from "void f(void) {}" with clang 3.5 and
; -gline-tables-only, so it contains old debug info.

; CHECK: WARNING: ignoring debug info with an invalid version (1) in {{.*}}/Inputs/drop-debug.bc
Work around pr23045 and make it easier to reproduce. Dropping old debug format requires the entire module to be read upfront. This was failing only with the gold plugin, but that is just because llvm-link was not upgrading metadata. The new testcase using llvm-link shows the problem. llvm-svn: 233381 2015-03-27 23:55:06 +08:00			`; RUN: llvm-link %p/Inputs/drop-debug.bc -o %t 2>&1 \| FileCheck %s`

			`;; drop-debug.bc was created from "void f(void) {}" with clang 3.5 and`
			`; -gline-tables-only, so it contains old debug info.`

Use diagnostic handler in the LLVMContext This patch converts code that has access to a LLVMContext to not take a diagnostic handler. This has a few advantages * It is easier to use a consistent diagnostic handler in a single program. * Less clutter since we are not passing a handler around. It does make it a bit awkward to implement some C APIs that return a diagnostic string. I will propose new versions of these APIs and deprecate the current ones. llvm-svn: 255571 2015-12-15 07:17:03 +08:00			`; CHECK: WARNING: ignoring debug info with an invalid version (1) in {{.*}}/Inputs/drop-debug.bc`