# REQUIRES: x86, shell

# Test that we don't erroneously replace \ with / on UNIX, as it's
# legal for a filename to contain backslashes.
# RUN: llvm-mc %s -o %T/foo\\.o -filetype=obj -triple=x86_64-pc-linux
# RUN: ld.lld %T/foo\\.o --reproduce %T/repro.tar -o /dev/null
# RUN: tar tf %T/repro.tar | FileCheck %s

# CHECK: repro/{{.*}}/foo\\.o

# REQUIRES: x86, shell

# Test that we don't erroneously replace \ with / on UNIX, as it's
# legal for a filename to contain backslashes.
# RUN: llvm-mc %s -o %T/foo\\.o -filetype=obj -triple=x86_64-pc-linux
# RUN: ld.lld %T/foo\\.o --reproduce %T/repro.tar -o /dev/null
# RUN: tar tf %T/repro.tar | FileCheck %s

# CHECK: repro/{{.*}}/foo\{{[\]?}}.o

Fix reproduce-blackslash.s test with NetBSD tar
[test] Fix reproduce-blackslash.s test with NetBSD tar

Unlike GNU tar and libarchive bsdtar, NetBSD 'tar -t' output does not
use C-style escapes and instead outputs paths literally.  Fix the test
to account both for escaped and literal backslash output.

Differential Revision: https://reviews.llvm.org/D55441

git-svn-id: f6089bf0e6284f307027cef4f64114ee9ebb0424@348628 91177308-0d34-0410-b5e6-96231b3b80d8
