================ @@ -0,0 +1,42 @@ +// RUN: rm -rf %t +// RUN: mkdir -p %t +// RUN: split-file %s %t + +// Step 1: Build PCH and defmap. +// RUN: %clang_cc1 -x c -emit-pch -fvalidate-ast-input-files-content -o %t/other.c.ast %t/other.c +// RUN: %clang_extdef_map %t/other.c -- -c -x c > %t/externalDefMap.tmp.txt +// RUN: sed 's| .*other\.c| other.c.ast|' %t/externalDefMap.tmp.txt > %t/externalDefMap.txt ---------------- necto wrote:
> Why? It's the way I am used to use `sed`. AFAIK, they are functionally equivalent, but perhaps `sed -e` is more explicit. It is also used more often across the tests, so I'll use it also: 0da55dc73c71 [NFC] use `sed -e` explicitly https://github.com/llvm/llvm-project/pull/196298 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
