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/driver.test

61 lines
2.3 KiB
Plaintext
Raw Normal View History

ELF: Do not exit if it cannot open an output file. It can fail to open an output file for various reasons, including lack of permission, too long filename, or the output file is not a mmap'able file. llvm-svn: 259596
2016-02-03 06:48:04 +08:00
# REQUIRES: x86
Allow joined options to fix http://llvm.org/pr26730. llvm-svn: 262550
2016-03-03 08:09:02 +08:00
# RUN: not ld.lld --unknown1 --unknown2 -m foo /no/such/file -lnosuchlib \
ELF: Add --version option. llvm-svn: 262167
2016-02-28 11:18:07 +08:00
# RUN: 2>&1 | FileCheck -check-prefix=UNKNOWN %s
Re-submit ELF: Report multiple errors from the driver. This reverts r259395 which reverted r259143. llvm-svn: 259572
2016-02-03 05:13:09 +08:00
Do not call warning() from ELFOptTable::parse(). warning() depends on Config->FatalWarnings, so we don't want to call that function before we initialize that member. llvm-svn: 274723
2016-07-07 09:58:04 +08:00
# UNKNOWN: unknown argument: --unknown1
# UNKNOWN: unknown argument: --unknown2
Recommit of r263252, [ELF] - Change all messages to lowercase to be consistent. which was reverted because included unrelative changes by mistake. Original commit message: [ELF] - Change all messages to lowercase to be consistent. That is directly opposite to http://reviews.llvm.org/D18045, which was reverted. This patch changes all messages to start from lowercase letter if they were not before. That is done to be consistent with clang. Differential revision: http://reviews.llvm.org/D18085 llvm-svn: 263337
2016-03-12 16:31:34 +08:00
# UNKNOWN: unknown emulation: foo
This reverts the r263125 It was discussed to make all messages be lowercase to be consistent with clang. (also reverts the r263128 which fixed build bot fail after r263125) Original commit message: [ELF] - Consistent spelling for error/warning messages Previously error and warnings were not consistent in lld. Some of them started from lowercase letter, others from uppercase. Also there was one or two which had a dot at the end. This patch changes all messages to start from uppercase letter if they were not before. Differential revision: http://reviews.llvm.org/D18045 llvm-svn: 263240
2016-03-11 22:43:02 +08:00
# UNKNOWN: cannot open /no/such/file
Recommit of r263252, [ELF] - Change all messages to lowercase to be consistent. which was reverted because included unrelative changes by mistake. Original commit message: [ELF] - Change all messages to lowercase to be consistent. That is directly opposite to http://reviews.llvm.org/D18045, which was reverted. This patch changes all messages to start from lowercase letter if they were not before. That is done to be consistent with clang. Differential revision: http://reviews.llvm.org/D18085 llvm-svn: 263337
2016-03-12 16:31:34 +08:00
# UNKNOWN: unable to find library -lnosuchlib
ELF: Do not exit if it cannot open an output file. It can fail to open an output file for various reasons, including lack of permission, too long filename, or the output file is not a mmap'able file. llvm-svn: 259596
2016-02-03 06:48:04 +08:00
# RUN: llvm-mc -filetype=obj -triple=x86_64-unknown-linux %s -o %t
ELF: Add --version option. llvm-svn: 262167
2016-02-28 11:18:07 +08:00
# RUN: not ld.lld %t -o /no/such/file 2>&1 | FileCheck -check-prefix=MISSING %s
[ELF] Fail the link early if an output path is invalid Patch from James Henderson. If a user has a long link, e.g. due to a large LTO link, they do not wish to run it and find that it failed because there was a mistake in their command-line, after they waited for some significant amount of time. This change adds some basic checking of the linker output file path, which is run shortly after parsing the command-line and linker script. An error is emitted if LLD cannot write to the specified path. Differential Revision: https://reviews.llvm.org/D30449 llvm-svn: 297645
2017-03-14 01:24:52 +08:00
# MISSING: cannot open output file /no/such/file
ELF: Do not exit if it cannot open an output file. It can fail to open an output file for various reasons, including lack of permission, too long filename, or the output file is not a mmap'able file. llvm-svn: 259596
2016-02-03 06:48:04 +08:00
ELF: Add --help option. llvm-svn: 262168
2016-02-28 11:18:09 +08:00
# RUN: ld.lld --help 2>&1 | FileCheck -check-prefix=HELP %s
# HELP: USAGE:
Fix Windows buildbots. llvm-svn: 298570
2017-03-23 09:16:57 +08:00
# HELP: : supported targets:{{.*}} elf
ELF: Add --help option. llvm-svn: 262168
2016-02-28 11:18:09 +08:00
[ELF] - Exit on --version call. GNU linkers disagree here. Though both -version and -v are mentioned in help to print the version information, GNU ld just normally exits, while gold can continue linking. We are compatible with ld.bfd here. This fixes PR31057. Differential revision: https://reviews.llvm.org/D26865 llvm-svn: 287448
2016-11-20 02:14:24 +08:00
# RUN: ld.lld --version 2>&1 | FileCheck -check-prefix=VERSION %s
Make the behavior of the -v option more closer to GNU linkers. Previously, lld exited with an error status if the only option given to the command was -v. GNU linkers gracefully exit in that case. This patch makes lld behave like GNU. Note that even with this patch, lld's -v and --version options behave slightly differently than GNU linkers' counterparts. For example, if you run `ld.bfd -v -v`, the version string is printed out twice. But that is an edge case that I don't think we need to take care of. Fixes https://bugs.llvm.org/show_bug.cgi?id=31582 Differential Revision: https://reviews.llvm.org/D40810 llvm-svn: 319717
2017-12-05 08:03:41 +08:00
# RUN: ld.lld -v 2>&1 | FileCheck -check-prefix=VERSION %s
# RUN: not ld.lld -v xyz 2>&1 | FileCheck -check-prefix=VERSION %s
Add "(compatible with GNU linkers)" to the -version output. Previous output: $ ld.lld -version LLD 5.0.0 New output: $ ld.lld -version LLD 5.0.0 (compatible with GNU linkers) Differential Revision: https://reviews.llvm.org/D31199 llvm-svn: 298532
2017-03-23 02:04:57 +08:00
# VERSION: LLD {{.*}} (compatible with GNU linkers)
ELF: Do not exit if it cannot open an output file. It can fail to open an output file for various reasons, including lack of permission, too long filename, or the output file is not a mmap'able file. llvm-svn: 259596
2016-02-03 06:48:04 +08:00
[ELF] - handle of command line options incompatible with -r Patch handles the command line options incompatible with relocatable output. Differential revision: http://reviews.llvm.org/D17758 llvm-svn: 262377
2016-03-02 03:38:51 +08:00
## Attempt to link DSO with -r
# RUN: ld.lld -shared %t -o %t.so
# RUN: not ld.lld -r %t.so %t -o %tfail 2>&1 | FileCheck -check-prefix=ERR %s
Recommit of r263252, [ELF] - Change all messages to lowercase to be consistent. which was reverted because included unrelative changes by mistake. Original commit message: [ELF] - Change all messages to lowercase to be consistent. That is directly opposite to http://reviews.llvm.org/D18045, which was reverted. This patch changes all messages to start from lowercase letter if they were not before. That is done to be consistent with clang. Differential revision: http://reviews.llvm.org/D18085 llvm-svn: 263337
2016-03-12 16:31:34 +08:00
# ERR: attempted static link of dynamic object
[ELF] - handle of command line options incompatible with -r Patch handles the command line options incompatible with relocatable output. Differential revision: http://reviews.llvm.org/D17758 llvm-svn: 262377
2016-03-02 03:38:51 +08:00
## Attempt to use -r and -shared together
# RUN: not ld.lld -r -shared %t -o %tfail 2>&1 | FileCheck -check-prefix=ERR2 %s
# ERR2: -r and -shared may not be used together
## Attempt to use -r and --gc-sections together
# RUN: not ld.lld -r --gc-sections %t -o %tfail 2>&1 | FileCheck -check-prefix=ERR3 %s
# ERR3: -r and --gc-sections may not be used together
## Attempt to use -r and --icf together
# RUN: not ld.lld -r --icf=all %t -o %tfail 2>&1 | FileCheck -check-prefix=ERR4 %s
# ERR4: -r and --icf may not be used together
[ELF] - -pie/--pic-executable option implemented -pie --pic-executable Create a position independent executable. This is currently only supported on ELF platforms. Position independent executables are similar to shared libraries in that they are relocated by the dynamic linker to the virtual address the OS chooses for them (which can vary between invocations). Like normal dynamically linked executables they can be executed and symbols defined in the executable cannot be overridden by shared libraries. Differential revision: http://reviews.llvm.org/D18183 llvm-svn: 263693
2016-03-17 13:57:33 +08:00
## Attempt to use -r and -pie together
# RUN: not ld.lld -r -pie %t -o %tfail 2>&1 | FileCheck -check-prefix=ERR5 %s
# ERR5: -r and -pie may not be used together
## Attempt to use -shared and -pie together
# RUN: not ld.lld -shared -pie %t -o %tfail 2>&1 | FileCheck -check-prefix=ERR6 %s
# ERR6: -shared and -pie may not be used together
Fix -output option. Usually, options that are longer than one character can be preceded either by "-" or "--", but options starting with "o" are exceptions because they conflict with "-o" option. They have to be preceded by "--". llvm-svn: 281004
2016-09-09 08:25:56 +08:00
## "--output=foo" is equivalent to "-o foo".
# RUN: not ld.lld %t --output=/no/such/file 2>&1 | FileCheck -check-prefix=ERR7 %s
[ELF] Fail the link early if an output path is invalid Patch from James Henderson. If a user has a long link, e.g. due to a large LTO link, they do not wish to run it and find that it failed because there was a mistake in their command-line, after they waited for some significant amount of time. This change adds some basic checking of the linker output file path, which is run shortly after parsing the command-line and linker script. An error is emitted if LLD cannot write to the specified path. Differential Revision: https://reviews.llvm.org/D30449 llvm-svn: 297645
2017-03-14 01:24:52 +08:00
# ERR7: cannot open output file /no/such/file
Fix -output option. Usually, options that are longer than one character can be preceded either by "-" or "--", but options starting with "o" are exceptions because they conflict with "-o" option. They have to be preceded by "--". llvm-svn: 281004
2016-09-09 08:25:56 +08:00
## "-output=foo" is equivalent to "-o utput=foo".
# RUN: not ld.lld %t -output=/no/such/file 2>&1 | FileCheck -check-prefix=ERR8 %s
[ELF] Fail the link early if an output path is invalid Patch from James Henderson. If a user has a long link, e.g. due to a large LTO link, they do not wish to run it and find that it failed because there was a mistake in their command-line, after they waited for some significant amount of time. This change adds some basic checking of the linker output file path, which is run shortly after parsing the command-line and linker script. An error is emitted if LLD cannot write to the specified path. Differential Revision: https://reviews.llvm.org/D30449 llvm-svn: 297645
2017-03-14 01:24:52 +08:00
# ERR8: cannot open output file utput=/no/such/file
Fix -output option. Usually, options that are longer than one character can be preceded either by "-" or "--", but options starting with "o" are exceptions because they conflict with "-o" option. They have to be preceded by "--". llvm-svn: 281004
2016-09-09 08:25:56 +08:00
ELF: Do not exit if it cannot open an output file. It can fail to open an output file for various reasons, including lack of permission, too long filename, or the output file is not a mmap'able file. llvm-svn: 259596
2016-02-03 06:48:04 +08:00
.globl _start
_start:
nop