llvm-project/lld/test/COFF/lto-late-arm.ll
Martin Storsjö 7f9a0048fa
[LLD] [COFF] Error out if new LTO objects are pulled in after the main LTO compilation (#71337)
Normally, this shouldn't happen. It can happen in exceptional
circumstances, if the compiled output of a bitcode object file
references symbols that weren't listed as undefined in the bitcode
object file itself.

This can at least happen in the following cases:
- A custom SEH personality is set via asm()
- Compiler generated calls to builtin helper functions, such as
__chkstk, or __rt_sdiv on arm

Both of these produce undefined references to symbols after compiling to
a regular object file, that aren't visible on the level of the IR object
file.

This is only an issue if the referenced symbols are provided as LTO
objects themselves; loading regular object files after the LTO
compilation works fine.

Custom SEH personalities are rare, but one CRT startup file in mingw-w64
does this. The referenced pesonality function is usually provided via an
import library, but for WinStore targets, a local dummy reimplementation
in C is used, which can be an LTO object.

Generated calls to builtins is very common, but the builtins aren't
usually provided as LTO objects (compiler-rt's builtins explicitly pass
-fno-lto when building), and many of the builtins are provided as raw .S
assembly files, which don't get built as LTO objects anyway, even if
built with -flto.

If hitting this unusual, but possible, situation, error out cleanly with
a clear message rather than crashing.
2023-11-07 11:49:40 +02:00

40 lines
1.3 KiB
LLVM

; REQUIRES: arm
;; A bitcode file can generate undefined references to symbols that weren't
;; listed as undefined on the bitcode file itself, when lowering produces
;; calls to e.g. builtin helper functions. If these functions are provided
;; as LTO bitcode, the linker would hit an unhandled state. (In practice,
;; compiler-rt builtins are always compiled with -fno-lto, so this shouldn't
;; happen.)
; RUN: rm -rf %t.dir
; RUN: split-file %s %t.dir
; RUN: llvm-as %t.dir/main.ll -o %t.main.obj
; RUN: llvm-as %t.dir/sdiv.ll -o %t.sdiv.obj
; RUN: llvm-ar rcs %t.sdiv.lib %t.sdiv.obj
; RUN: env LLD_IN_TEST=1 not lld-link /entry:entry %t.main.obj %t.sdiv.lib /out:%t.exe /subsystem:console 2>&1 | FileCheck %s
; CHECK: error: LTO object file lto-late-arm.ll.tmp.sdiv.lib(lto-late-arm.ll.tmp.sdiv.obj) linked in after doing LTO compilation.
;--- main.ll
target datalayout = "e-m:w-p:32:32-Fi8-i64:64-v128:64:128-a:0:32-n32-S64"
target triple = "thumbv7-w64-windows-gnu"
@num = dso_local global i32 100
define dso_local arm_aapcs_vfpcc i32 @entry(i32 %param) {
entry:
%0 = load i32, ptr @num
%div = sdiv i32 %0, %param
ret i32 %div
}
;--- sdiv.ll
target datalayout = "e-m:w-p:32:32-Fi8-i64:64-v128:64:128-a:0:32-n32-S64"
target triple = "thumbv7-w64-windows-gnu"
define dso_local arm_aapcs_vfpcc void @__rt_sdiv() {
entry:
ret void
}