Files
swift-mirror/test/Driver/driver_mode.swift
Jordan Rose 6d9b5cb8ed [Driver] Factor interpret-script mode out into a separate Action.
This makes it easier to make interpreter modes behave differently from
compilation modes. Obviously that's a trade-off, since the two modes also
share plenty, but given how few of the existing CompileJobAction checks had
to be modified for the new InterpretJobAction, I think this is the right
way to go.

Groundwork for setting [DY]LD_LIBRARY_PATH ahead of time when invoking the
interpreter, which is rdar://problem/23588774.
2015-12-04 12:18:45 -08:00

15 lines
736 B
Swift

// RUN: %swift_driver_plain --driver-mode=swiftc -driver-print-actions %s 2>&1 | FileCheck -check-prefix=CHECK-SWIFTC-%target-object-format %s
// RUN: %swift_driver_plain -driver-print-actions %s --driver-mode=swiftc 2>&1 | FileCheck -check-prefix=CHECK-SWIFT %s
// CHECK-SWIFTC-macho: 0: input, "{{.*}}driver_mode.swift", swift
// CHECK-SWIFTC-macho: 1: compile, {0}, object
// CHECK-SWIFTC-macho: 2: link, {1}, image
// CHECK-SWIFTC-elf: 0: input, "{{.*}}driver_mode.swift", swift
// CHECK-SWIFTC-elf: 1: compile, {0}, object
// CHECK-SWIFTC-elf: 2: swift-autolink-extract, {1}, autolink
// CHECK-SWIFTC-elf: 3: link, {1, 2}, image
// CHECK-SWIFT: 0: input, "{{.*}}driver_mode.swift", swift
// CHECK-SWIFT: 1: interpret, {0}, none