Hack Around Incremental Test Mod Times Bugs In Binutils

Modification times are not accurately maintained by tools like cp. Touch
these build products explicitly to kick the incremental machinery into
gear.

Author: CodaFi

test/Incremental/CrossModule/external-cascade.swift

@@ -1,12 +1,6 @@
 // RUN: %empty-directory(%t)
 // RUN: cp -r %S/Inputs/external-cascade/* %t
 
-// No reason to run these tests on the simulator hosts rdar://70772320
-// UNSUPPORTED: CPU=x86_64 && OS=ios
-// UNSUPPORTED: CPU=x86_64 && OS=tvos
-// UNSUPPORTED: CPU=x86_64 && OS=watchos
-// UNSUPPORTED: CPU=i386 && OS=watchos
-
 //
 // This test establishes a chain of modules that all depend on a set of
 // bridging headers. This test ensures that changes to external dependencies -
@@ -32,6 +26,7 @@
 
 // RUN: rm %t/another-header.h
 // RUN: cp %S/Inputs/external-cascade/another-header.h %t/another-header.h
+// RUN: touch %t/another-header.h
 // RUN: cd %t && %target-swiftc_driver -c -incremental -emit-dependencies -emit-module -emit-module-path %t/C.swiftmodule -enable-experimental-cross-module-incremental-build -module-name C -I %t -output-file-map %t/C.json -working-directory %t -import-objc-header %t/bridging-header.h -Xfrontend -validate-tbd-against-ir=none -driver-show-incremental -driver-show-job-lifecycle C.swift 2>&1 | %FileCheck -check-prefix MODULE-C %s
 // RUN: cd %t && %target-swiftc_driver -c -incremental -emit-dependencies -emit-module -emit-module-path %t/B.swiftmodule -enable-experimental-cross-module-incremental-build -module-name B -I %t -output-file-map %t/B.json -working-directory %t -driver-show-incremental -driver-show-job-lifecycle B.swift 2>&1 | %FileCheck -check-prefix MODULE-B %s
 // RUN: cd %t && %target-swiftc_driver -c -incremental -emit-dependencies -emit-module -emit-module-path %t/A.swiftmodule -enable-experimental-cross-module-incremental-build -module-name A -I %t -output-file-map %t/A.json -working-directory %t -driver-show-incremental -driver-show-job-lifecycle A.swift 2>&1 | %FileCheck -check-prefix MODULE-A %s

test/Incremental/CrossModule/linear.swift

@@ -1,12 +1,6 @@
 // RUN: %empty-directory(%t)
 // RUN: cp -r %S/Inputs/linear/* %t
 
-// No reason to run these tests on the simulator hosts rdar://70772320
-// UNSUPPORTED: CPU=x86_64 && OS=ios
-// UNSUPPORTED: CPU=x86_64 && OS=tvos
-// UNSUPPORTED: CPU=x86_64 && OS=watchos
-// UNSUPPORTED: CPU=i386 && OS=watchos
-
 //
 // This test establishes a "linear" chain of modules that import one another
 // and ensures that a cross-module incremental build does not needlessly
@@ -31,6 +25,7 @@
 //
 
 // RUN: cd %t && %target-swiftc_driver -c -incremental -emit-dependencies -emit-module -emit-module-path %t/C.swiftmodule -enable-experimental-cross-module-incremental-build -module-name C -I %t -output-file-map %t/C.json -working-directory %t -driver-show-incremental -driver-show-job-lifecycle -DNEW C.swift 2>&1 | %FileCheck -check-prefix MODULE-C %s
+// RUN: touch %t/C.swiftmodule
 // RUN: cd %t && %target-swiftc_driver -c -incremental -emit-dependencies -emit-module -emit-module-path %t/B.swiftmodule -enable-experimental-cross-module-incremental-build -module-name B -I %t -output-file-map %t/B.json -working-directory %t -driver-show-incremental -driver-show-job-lifecycle B.swift 2>&1 | %FileCheck -check-prefix MODULE-B %s
 // RUN: cd %t && %target-swiftc_driver -c -incremental -emit-dependencies -emit-module -emit-module-path %t/A.swiftmodule -enable-experimental-cross-module-incremental-build -module-name A -I %t -output-file-map %t/A.json -working-directory %t -driver-show-incremental -driver-show-job-lifecycle A.swift 2>&1 | %FileCheck -check-prefix MODULE-A %s
 

test/Incremental/CrossModule/transitive.swift

@@ -1,12 +1,6 @@
 // RUN: %empty-directory(%t)
 // RUN: cp -r %S/Inputs/transitive/* %t
 
-// No reason to run these tests on the simulator hosts rdar://70772320
-// UNSUPPORTED: CPU=x86_64 && OS=ios
-// UNSUPPORTED: CPU=x86_64 && OS=tvos
-// UNSUPPORTED: CPU=x86_64 && OS=watchos
-// UNSUPPORTED: CPU=i386 && OS=watchos
-
 //
 // This test establishes a "transitive" chain of modules that import one another
 // and ensures that a cross-module incremental build rebuilds all modules
@@ -33,6 +27,7 @@
 //
 
 // RUN: cd %t && %target-swiftc_driver -c -incremental -emit-dependencies -emit-module -emit-module-path %t/C.swiftmodule -enable-experimental-cross-module-incremental-build -module-name C -I %t -output-file-map %t/C.json -working-directory %t -driver-show-incremental -driver-show-job-lifecycle -DUSEC -DNEW C.swift 2>&1 | %FileCheck -check-prefix MODULE-C %s
+// RUN: touch %t/C.swiftmodule
 // RUN: cd %t && %target-swiftc_driver -c -incremental -emit-dependencies -emit-module -emit-module-path %t/B.swiftmodule -enable-experimental-cross-module-incremental-build -module-name B -I %t -output-file-map %t/B.json -working-directory %t -driver-show-incremental -driver-show-job-lifecycle -DUSEC B.swift 2>&1 | %FileCheck -check-prefix MODULE-B %s
 // RUN: cd %t && %target-swiftc_driver -c -incremental -emit-dependencies -emit-module -emit-module-path %t/A.swiftmodule -enable-experimental-cross-module-incremental-build -module-name A -I %t -output-file-map %t/A.json -working-directory %t -driver-show-incremental -driver-show-job-lifecycle -DUSEC A.swift 2>&1 | %FileCheck -check-prefix MODULE-A %s