mirror of
https://github.com/llvm/llvm-project.git
synced 2025-04-16 21:56:34 +00:00

The export names are saved as StringRefs pointing into the COFF directives. In the case of LTO objects, this can be memory allocated that is owned by the LTO InputFile, which gets destructed when doing the compilation. In the case of LTO objects from an older version of LLVM, which require being upgraded when loaded, the directives string gets destructed, while when using LTO objects of a matching version (the common case), the directives string points into memory that doesn't get destructed on LTO compilation. Test this by linking a bundled binary LTO object file, from an older version of LLVM. This fixes issue #78591, and downstream issue https://github.com/mstorsjo/llvm-mingw/issues/392.
16 lines
542 B
Plaintext
16 lines
542 B
Plaintext
; REQUIRES: x86
|
|
|
|
;; Test linking an LTO object file that contains directives. The
|
|
;; LTO object file is built with an older toolchain, to force it
|
|
;; to be upgraded when loaded.
|
|
|
|
;; The input file is compiled from source that looks like this:
|
|
;; void __declspec(dllexport) entry(void) { }
|
|
;; with this command:
|
|
;; clang -target x86_64-windows-msvc -c main.c -flto
|
|
|
|
; RUN: lld-link /entry:entry /subsystem:console %p/Inputs/lto-directives.obj /dll /out:%t.dll
|
|
; RUN: llvm-readobj --coff-exports %t.dll | FileCheck %s
|
|
|
|
; CHECK: Name: entry
|