Introduce -unavailable-decl-optimization
#64644
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduce the
-unavailable-decl-optimization
frontend flag which can be used to reduce the size of a compiled binary by removing machine code related to declarations that are marked unavailable with an@available
attribute. Unavailable code is meant to be provably unreachable at runtime for a specific execution context and therefore including machine code for these declarations is wasteful.In this iteration, the flag supports two modes:
none
: Does not remove any code related to unavailable declarations. This is the default.complete
: Avoids generating any machine code for unavailable declarations. This will be the most aggressive optimization available.The plan is to expand the available modes in the future with at least one more option,
stub
, which will cause unavailable functions to be emitted as stubs containing justfatalError()
. This option will be needed by owners of resilient libraries to preserve ABI compatibility since existing clients may link against the symbols for unavailable declarations, even if they never execute them.Resolves rdar://106674022