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/early-exit-for-bad-paths.s

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

36 lines
1.4 KiB
ArmAsm
Raw Normal View History

[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
# REQUIRES: x86
# RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %s -o %t.o
# RUN: not ld.lld %t.o -o does_not_exist/output 2>&1 | \
[ELF] Fail the link early if the map file path is invalid As with the changes made in r297645, we do not want a potentially long link to be run, if it will ultimately fail because the map file is not writable. This change reuses the same functionality as the output file path check. See https://reviews.llvm.org/D30449 for further justification and explanations. Reviewers: ruiu Differential Revision: https://reviews.llvm.org/D31603 llvm-svn: 299420
2017-04-04 17:42:24 +08:00
# RUN: FileCheck %s -check-prefixes=NO-DIR-OUTPUT,CHECK
[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
# RUN: not ld.lld %t.o -o %s/dir_is_a_file 2>&1 | \
[ELF] Fail the link early if the map file path is invalid As with the changes made in r297645, we do not want a potentially long link to be run, if it will ultimately fail because the map file is not writable. This change reuses the same functionality as the output file path check. See https://reviews.llvm.org/D30449 for further justification and explanations. Reviewers: ruiu Differential Revision: https://reviews.llvm.org/D31603 llvm-svn: 299420
2017-04-04 17:42:24 +08:00
# RUN: FileCheck %s -check-prefixes=DIR-IS-OUTPUT,CHECK
[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
# RUN: echo "OUTPUT(\"does_not_exist/output\")" > %t.script
# RUN: not ld.lld %t.o %t.script 2>&1 | \
[ELF] Fail the link early if the map file path is invalid As with the changes made in r297645, we do not want a potentially long link to be run, if it will ultimately fail because the map file is not writable. This change reuses the same functionality as the output file path check. See https://reviews.llvm.org/D30449 for further justification and explanations. Reviewers: ruiu Differential Revision: https://reviews.llvm.org/D31603 llvm-svn: 299420
2017-04-04 17:42:24 +08:00
# RUN: FileCheck %s -check-prefixes=NO-DIR-OUTPUT,CHECK
[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
# RUN: echo "OUTPUT(\"%s/dir_is_a_file\")" > %t.script
# RUN: not ld.lld %t.o %t.script 2>&1 | \
[ELF] Fail the link early if the map file path is invalid As with the changes made in r297645, we do not want a potentially long link to be run, if it will ultimately fail because the map file is not writable. This change reuses the same functionality as the output file path check. See https://reviews.llvm.org/D30449 for further justification and explanations. Reviewers: ruiu Differential Revision: https://reviews.llvm.org/D31603 llvm-svn: 299420
2017-04-04 17:42:24 +08:00
# RUN: FileCheck %s -check-prefixes=DIR-IS-OUTPUT,CHECK
[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
[ELF] Fail the link early if the map file path is invalid As with the changes made in r297645, we do not want a potentially long link to be run, if it will ultimately fail because the map file is not writable. This change reuses the same functionality as the output file path check. See https://reviews.llvm.org/D30449 for further justification and explanations. Reviewers: ruiu Differential Revision: https://reviews.llvm.org/D31603 llvm-svn: 299420
2017-04-04 17:42:24 +08:00
# RUN: not ld.lld %t.o -o %t -Map=does_not_exist/output 2>&1 | \
# RUN: FileCheck %s -check-prefixes=NO-DIR-MAP,CHECK
# RUN: not ld.lld %t.o -o %t -Map=%s/dir_is_a_file 2>&1 | \
# RUN: FileCheck %s -check-prefixes=DIR-IS-MAP,CHECK
# NO-DIR-OUTPUT: error: cannot open output file does_not_exist/output:
# DIR-IS-OUTPUT: error: cannot open output file {{.*}}/dir_is_a_file:
# NO-DIR-MAP: error: cannot open map file does_not_exist/output:
# DIR-IS-MAP: error: cannot open map file {{.*}}/dir_is_a_file:
[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
# We should exit before doing the actual link. If an undefined symbol error is
# discovered we haven't bailed out early as expected.
# CHECK-NOT: undefined_symbol
[ELF] Fail the link early if the map file path is invalid As with the changes made in r297645, we do not want a potentially long link to be run, if it will ultimately fail because the map file is not writable. This change reuses the same functionality as the output file path check. See https://reviews.llvm.org/D30449 for further justification and explanations. Reviewers: ruiu Differential Revision: https://reviews.llvm.org/D31603 llvm-svn: 299420
2017-04-04 17:42:24 +08:00
# RUN: not ld.lld %t.o -o / 2>&1 | FileCheck %s -check-prefixes=ROOT,CHECK
Make FileOutputBuffer fail early if you pass a directory. Previously, it created a temporary directory and then failed when FileOutputBuffer tried to rename that file to the destination file (which is actually a directory name). Differential Revision: https://reviews.llvm.org/D30912 llvm-svn: 297679
2017-03-14 06:19:05 +08:00
# ROOT: error: cannot open output file /
[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
.globl _start
_start:
call undefined_symbol