mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
da07ff577c
PrintAsClang is supposed to emit declarations in the same order regardless of the compiler’s internal state, but we have repeatedly found that our current criteria are inadequate, resulting in non-functionality-affecting changes to generated header content. Add a diagnostic that’s emitted when this happens soliciting a bug report. Since there *should* be no cases where the compiler fails to order declarations, this diagnostic is never actually emitted. Instead, we test this change by enabling `-verify` on nearly all PrintAsClang tests to make sure they are unaffected. This did demonstrate a missing criterion that only mattered in C++ mode: extensions that varied only in their generic signature were not sorted stably. Add a sort criterion for this.
13 lines
1.0 KiB
Swift
13 lines
1.0 KiB
Swift
// RUN: %empty-directory(%t)
|
|
// RUN: cp -r %S/Inputs/CrossCompiler.framework %t/
|
|
// RUN: %target-swift-frontend(mock-sdk: %clang-importer-sdk) %S/../Inputs/empty.swift -typecheck -verify -emit-objc-header-path %t/CrossCompiler.framework/Headers/empty.h
|
|
// RUN: %target-swift-frontend(mock-sdk: %clang-importer-sdk) -enable-objc-interop -emit-module-path %t/CrossCompiler.framework/Modules/CrossCompiler.swiftmodule/%target-swiftmodule-name -import-underlying-module -F %t -F %clang-importer-sdk-path/frameworks -module-name CrossCompiler -disable-objc-attr-requires-foundation-module -parse-as-library %s -Xcc -Werror
|
|
|
|
// Ensure that building with multiple compatibility headers from different compilers doesn't
|
|
// trigger "macro redefinition" errors (rdar://106087804)
|
|
|
|
// CrossCompiler.framework contains a modified header generated with Swift 5.7 (before the
|
|
// PrintAsClang refactor to make macros data-driven). By compiling it alongside a freshly-generated
|
|
// header, we can make sure that the macro definitions are the same before and after the switch.
|
|
|