mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
2dbd6cc56b
Introduce two modes of bridging: * inline mode: this is basically how it worked so far. Using full C++ interop which allows bridging functions to be inlined. * pure mode: bridging functions are not inlined but compiled in a cpp file. This allows to reduce the C++ interop requirements to a minimum. No std/llvm/swift headers are imported. This change requires a major refactoring of bridging sources. The implementation of bridging functions go to two separate files: SILBridgingImpl.h and OptimizerBridgingImpl.h. Depending on the mode, those files are either included in the corresponding header files (inline mode), or included in the c++ file (pure mode). The mode can be selected with the BRIDGING_MODE cmake variable. By default it is set to the inline mode (= existing behavior). The pure mode is only selected in certain configurations to work around C++ interop issues: * In debug builds, to workaround a problem with LLDB's `po` command (rdar://115770255). * On windows to workaround a build problem.
36 lines
586 B
Plaintext
36 lines
586 B
Plaintext
module BasicBridging {
|
|
header "swift/Basic/BasicBridging.h"
|
|
requires cplusplus
|
|
export *
|
|
}
|
|
|
|
module CBasicBridging {
|
|
header "swift/Basic/CBasicBridging.h"
|
|
}
|
|
|
|
module ASTBridging {
|
|
header "swift/AST/ASTBridging.h"
|
|
requires cplusplus
|
|
export *
|
|
}
|
|
|
|
module CASTBridging {
|
|
header "swift/AST/CASTBridging.h"
|
|
}
|
|
|
|
module SILBridging {
|
|
header "swift/SIL/SILBridging.h"
|
|
requires cplusplus
|
|
export *
|
|
}
|
|
|
|
module OptimizerBridging {
|
|
header "swift/SILOptimizer/OptimizerBridging.h"
|
|
export *
|
|
}
|
|
|
|
module _RegexParserBridging {
|
|
header "swift/Parse/RegexParserBridging.h"
|
|
export *
|
|
}
|