maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lld/test/ELF/lto/archive-no-index.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

35 lines
1023 B
LLVM
Raw Normal View History

COFF: include archive name in LTO object name Summary: In the ELF linker, we create the buffer identifier for bitcode files by appending the object name to the archive name. This change makes the COFF linker do the same. Without the change, ThinLTO builds can fail with an error message about multiple ThinLTO modules per object file, caused by object files contained in different archives having the same name. Reviewers: pcc, ruiu Reviewed By: pcc Subscribers: mehdi_amini Differential Revision: https://reviews.llvm.org/D31402 llvm-svn: 298942
2017-03-29 05:20:06 +08:00
; REQUIRES: x86
Make a hack for LTO work only when you are actually doing LTO. We allow an archive file without symbol table as a linker input as a workaround for a very common error in LTO build. But that logic worked even for an archive file containing non-bitcode files, which is not expected. This patch limits that workaround to one that contains only bitcode files. Differential Revision: https://reviews.llvm.org/D59373 llvm-svn: 356186
2019-03-15 02:21:32 +08:00
; Tests that we accept an archive file without symbol table
; if all the member files are bitcode files.
COFF: include archive name in LTO object name Summary: In the ELF linker, we create the buffer identifier for bitcode files by appending the object name to the archive name. This change makes the COFF linker do the same. Without the change, ThinLTO builds can fail with an error message about multiple ThinLTO modules per object file, caused by object files contained in different archives having the same name. Reviewers: pcc, ruiu Reviewed By: pcc Subscribers: mehdi_amini Differential Revision: https://reviews.llvm.org/D31402 llvm-svn: 298942
2017-03-29 05:20:06 +08:00
Accept archive files with no symbol table instad of warning on them. It seems virtually everyone who tries to do LTO build with Clang and LLD was hit by a mistake to forget using llvm-ar command to create archive files. I wasn't an exception. Since this is an annoying common issue, it is probably better to handle that gracefully rather than reporting an error and tell the user to redo build with different configuration. Differential Revision: https://reviews.llvm.org/D32721 llvm-svn: 302083
2017-05-04 05:03:08 +08:00
; RUN: llvm-as -o %t1.o %s
; RUN: llvm-as -o %t2.o %S/Inputs/archive.ll
COFF: include archive name in LTO object name Summary: In the ELF linker, we create the buffer identifier for bitcode files by appending the object name to the archive name. This change makes the COFF linker do the same. Without the change, ThinLTO builds can fail with an error message about multiple ThinLTO modules per object file, caused by object files contained in different archives having the same name. Reviewers: pcc, ruiu Reviewed By: pcc Subscribers: mehdi_amini Differential Revision: https://reviews.llvm.org/D31402 llvm-svn: 298942
2017-03-29 05:20:06 +08:00
Accept archive files with no symbol table instad of warning on them. It seems virtually everyone who tries to do LTO build with Clang and LLD was hit by a mistake to forget using llvm-ar command to create archive files. I wasn't an exception. Since this is an annoying common issue, it is probably better to handle that gracefully rather than reporting an error and tell the user to redo build with different configuration. Differential Revision: https://reviews.llvm.org/D32721 llvm-svn: 302083
2017-05-04 05:03:08 +08:00
; RUN: rm -f %t1.a %t2.a
; RUN: llvm-ar crS %t1.a %t2.o
; RUN: llvm-ar crs %t2.a %t2.o
COFF: include archive name in LTO object name Summary: In the ELF linker, we create the buffer identifier for bitcode files by appending the object name to the archive name. This change makes the COFF linker do the same. Without the change, ThinLTO builds can fail with an error message about multiple ThinLTO modules per object file, caused by object files contained in different archives having the same name. Reviewers: pcc, ruiu Reviewed By: pcc Subscribers: mehdi_amini Differential Revision: https://reviews.llvm.org/D31402 llvm-svn: 298942
2017-03-29 05:20:06 +08:00
[ELF] Remove -m argument to lld in test files. NFC. This should be correctly implied by the linker. This also makes the tests slightly easier to maintain and compare with the equivalent tests under for other platforms. Differential Revision: https://reviews.llvm.org/D47513 llvm-svn: 333567
2018-05-31 01:57:08 +08:00
; RUN: ld.lld -o %t -emain %t1.o %t1.a
; RUN: ld.lld -o %t -emain %t1.o %t2.a
COFF: include archive name in LTO object name Summary: In the ELF linker, we create the buffer identifier for bitcode files by appending the object name to the archive name. This change makes the COFF linker do the same. Without the change, ThinLTO builds can fail with an error message about multiple ThinLTO modules per object file, caused by object files contained in different archives having the same name. Reviewers: pcc, ruiu Reviewed By: pcc Subscribers: mehdi_amini Differential Revision: https://reviews.llvm.org/D31402 llvm-svn: 298942
2017-03-29 05:20:06 +08:00
Reland "Change the X86 datalayout to add three address spaces for 32 bit signed, 32 bit unsigned, and 64 bit pointers." This reverts 57076d3199fc2b0af4a3736b7749dd5462cacda5. Original review at https://reviews.llvm.org/D64931. Review for added fix at https://reviews.llvm.org/D66843. llvm-svn: 371568
2019-09-11 07:15:38 +08:00
target datalayout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128"
COFF: include archive name in LTO object name Summary: In the ELF linker, we create the buffer identifier for bitcode files by appending the object name to the archive name. This change makes the COFF linker do the same. Without the change, ThinLTO builds can fail with an error message about multiple ThinLTO modules per object file, caused by object files contained in different archives having the same name. Reviewers: pcc, ruiu Reviewed By: pcc Subscribers: mehdi_amini Differential Revision: https://reviews.llvm.org/D31402 llvm-svn: 298942
2017-03-29 05:20:06 +08:00
target triple = "x86_64-unknown-linux-gnu"
declare void @f()
define i32 @main() {
call void @f()
ret i32 0
}
Make a hack for LTO work only when you are actually doing LTO. We allow an archive file without symbol table as a linker input as a workaround for a very common error in LTO build. But that logic worked even for an archive file containing non-bitcode files, which is not expected. This patch limits that workaround to one that contains only bitcode files. Differential Revision: https://reviews.llvm.org/D59373 llvm-svn: 356186
2019-03-15 02:21:32 +08:00
; RUN: echo 'f:' | llvm-mc -triple=x86_64-pc-linux -filetype=obj - -o %t3.o
; RUN: rm -f %t3.a
; RUN: llvm-ar crS %t3.a %t3.o
; RUN: not ld.lld -o /dev/null -emain %t1.o %t3.a 2>&1 | FileCheck -check-prefix=ERR1 %s
[ELF] Error on archive with missing index This matches the wasm lld and GNU ld behavior. The ELF linker has special handling for bitcode archives but if that doesn't kick in we probably want to error out rather than silently ignore the library. Differential Revision: https://reviews.llvm.org/D63781 llvm-svn: 364998
2019-07-03 10:29:02 +08:00
; ERR1: error: {{.*}}.a: archive has no index; run ranlib to add one
Make a hack for LTO work only when you are actually doing LTO. We allow an archive file without symbol table as a linker input as a workaround for a very common error in LTO build. But that logic worked even for an archive file containing non-bitcode files, which is not expected. This patch limits that workaround to one that contains only bitcode files. Differential Revision: https://reviews.llvm.org/D59373 llvm-svn: 356186
2019-03-15 02:21:32 +08:00
; RUN: rm -f %t4.a
; RUN: llvm-ar cr %t4.a
; RUN: not ld.lld -o /dev/null -emain %t1.o %t4.a 2>&1 | FileCheck -check-prefix=ERR2 %s
; ERR2: error: undefined symbol: f