mirror of
https://github.com/apple/swift.git
synced 2025-12-21 12:14:44 +01:00
3859ae6db6
Unlike the frontend, the driver doesn't account for any VFS overlays set up by the -vfsoverlay option when processing its input files. It also errors if any of those input files don't exist on the file system. This makes it impossible to use a file that only exists in the VFS as input to the driver, even though the same file would be handled without issue by the frontend. If the file doesn't exist even accounting for the VFS the frontend emits a missing file diagnostic, so this change just suppresses the existence check for inputs when a -vfsoverlay option is present. Resolves rdar://problem/72485443
14 lines
1.1 KiB
Swift
14 lines
1.1 KiB
Swift
// Verifies that the driver passes the -vfsoverlay flag to the frontend (SR-12834).
|
|
// RUN: %swiftc_driver -driver-print-jobs -c -vfsoverlay overlay.yaml %s | %FileCheck --check-prefix=CHECK-ONE %s
|
|
|
|
// CHECK-ONE: bin{{/|\\\\}}swift{{(-frontend|c)?(\.exe)?"?}} -frontend{{.*}}-c{{.*}}-vfsoverlay overlay.yaml
|
|
|
|
// Verifies that multiple occurrences are passed in order.
|
|
// RUN: %swiftc_driver -driver-print-jobs -c -vfsoverlay overlay1.yaml -vfsoverlay overlay2.yaml -vfsoverlay overlay3.yaml %s | %FileCheck --check-prefix=CHECK-MULTIPLE %s
|
|
|
|
// CHECK-MULTIPLE: bin{{/|\\\\}}swift{{(-frontend|c)?(\.exe)?"?}} -frontend{{.*}}-c{{.*}}-vfsoverlay overlay1.yaml -vfsoverlay overlay2.yaml -vfsoverlay overlay3.yaml
|
|
|
|
// Verifies that input paths are not rejected prematurely when -vfsoverlay is present as they may exist on the vfs (which the frontend accounts for) even if they don't exist on the real file system.
|
|
// RUN: not %swiftc_driver -driver-print-jobs -c %t/file-not-on-the-real-filesystem.swift
|
|
// RUN: %swiftc_driver -driver-print-jobs -c -vfsoverlay overlay1.yaml %t/file-not-on-the-real-filesystem.swift
|