Ensure that verbose (-v) mode applies to in-place execution.

[artemcm]

For compiles which fall under our "in-place execution" flow, ensure that we print the in-place job before executing it if -v was specified.

Resolves rdar://79295614

[artemcm]

@swift-ci please test

[artemcm]

@swift-ci please test

[artemcm]

From https://ci.swift.org/job/pr-swift-driver-macos/1255/console:

failed: caught error: "signalled(9): 

Hmm, I get the same error when this test invokes swift-frontend from the latest snapshot (June 13, 2021), but not other compilers. Perhaps there is something wrong with this build.

[artemcm]

From https://ci.swift.org/job/pr-swift-driver-macos/1255/console:

failed: caught error: "signalled(9): 

Hmm, I get the same error when this test invokes swift-frontend from the latest snapshot (June 13, 2021), but not other compilers. Perhaps there is something wrong with this build.

It looks like toolchains on swift.org do not have a functioning immediate mode (swift test.swift or directly swift-frontend -interpret) due to a code-signing issue. 😢 That needs to be figured out first before a test like the one in this PR can work.

[artemcm]

From https://ci.swift.org/job/pr-swift-driver-macos/1255/console:

failed: caught error: "signalled(9): 

Hmm, I get the same error when this test invokes swift-frontend from the latest snapshot (June 13, 2021), but not other compilers. Perhaps there is something wrong with this build.

It looks like toolchains on swift.org do not have a functioning immediate mode (swift test.swift or directly swift-frontend -interpret) due to a code-signing issue. 😢 That needs to be figured out first before a test like the one in this PR can work.

Toolchains on swift.org should now have their code-signing issues resolved, so as soon as there is a new development snapshot published, this should be good to go.

[artemcm]

@swift-ci please test