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/reproduce-error.s

16 lines
418 B
ArmAsm
Raw Normal View History

Disable cpio test on Windows again. The last fix is unlikely to solve the issue. Reverting it to the original file. llvm-svn: 286393
2016-11-10 04:54:01 +08:00
# Extracting the cpio archive can get over the path limit on windows.
# REQUIRES: shell
Produce cpio files for --reproduce. We want --reproduce to * not rewrite scripts and thin archives * work with absolute paths Given that, it pretty much has to create a full directory tree. On windows that is problematic because of the very short maximum path limit. On most cases users can still work around it with "--repro c:\r", but that is annoying and not viable for automated testing. We then need to produce some form of archive with the files. The first option that comes to mind is .a files since we already have code for writing them. There are a few problems with them The format has a dedicated string table, so we cannot start writing it until all members are known. Regular implementations don't support creating directories. We could make llvm-ar support that, but that is probably not a good idea. The next natural option would be tar. The problem is that to support long path names (which is how this started) it needs a "pax extended header" making this an annoying format to write. The next option I looked at seems a natural fit: cpio files. They are available on pretty much every unix, support directories and long path names and are really easy to write. The only slightly annoying part is a terminator, but at least gnu cpio only prints a warning if it is missing, which is handy for crashes. This patch still makes an effort to always create it. llvm-svn: 268404
2016-05-04 01:30:44 +08:00
# RUN: rm -rf %t.dir
# RUN: mkdir -p %t.dir
# RUN: cd %t.dir
# RUN: not ld.lld --reproduce repro abc -o t 2>&1 | FileCheck %s
# CHECK: cannot open abc: {{N|n}}o such file or directory
# RUN: grep TRAILER repro.cpio
Attempt to fix green dragon bot. llvm-svn: 286392
2016-11-10 04:42:34 +08:00
# RUN: cpio -id < repro.cpio
Disable cpio test on Windows again. The last fix is unlikely to solve the issue. Reverting it to the original file. llvm-svn: 286393
2016-11-10 04:54:01 +08:00
# RUN: FileCheck --check-prefix=RSP %s < repro/response.txt
Produce cpio files for --reproduce. We want --reproduce to * not rewrite scripts and thin archives * work with absolute paths Given that, it pretty much has to create a full directory tree. On windows that is problematic because of the very short maximum path limit. On most cases users can still work around it with "--repro c:\r", but that is annoying and not viable for automated testing. We then need to produce some form of archive with the files. The first option that comes to mind is .a files since we already have code for writing them. There are a few problems with them The format has a dedicated string table, so we cannot start writing it until all members are known. Regular implementations don't support creating directories. We could make llvm-ar support that, but that is probably not a good idea. The next natural option would be tar. The problem is that to support long path names (which is how this started) it needs a "pax extended header" making this an annoying format to write. The next option I looked at seems a natural fit: cpio files. They are available on pretty much every unix, support directories and long path names and are really easy to write. The only slightly annoying part is a terminator, but at least gnu cpio only prints a warning if it is missing, which is handy for crashes. This patch still makes an effort to always create it. llvm-svn: 268404
2016-05-04 01:30:44 +08:00
# RSP: abc
# RSP: -o t