Skip to content

[Regex] Build _RegexParser without resilience #58810

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 13, 2022

Conversation

rxwei
Copy link
Contributor

@rxwei rxwei commented May 11, 2022

_RegexParser does not need resilience as it's only ever going to be used by _StringProcessing and RegexBuilder. It's version-locked with its dependent modules.

Resolves rdar://93067204.

_RegexParser does not need resilience as it's only ever going to be used by _StringProcessing and RegexBuilder. It's version-locked with its dependent modules.

Resolves rdar://93067204.
@rxwei
Copy link
Contributor Author

rxwei commented May 11, 2022

@swift-ci please test

@rxwei rxwei marked this pull request as ready for review May 12, 2022 18:33
@rxwei rxwei requested review from milseman and stephentyrone May 12, 2022 18:33
Copy link
Member

@milseman milseman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would this have any impact or risk when it comes time for compiler integration?

@rxwei
Copy link
Contributor Author

rxwei commented May 13, 2022

Would this have any impact or risk when it comes time for compiler integration?

This doesn't change how the copy of _RegexParser is built in SwiftCompilerSources. That copy is always built without resilience.

@rxwei rxwei merged commit fb38fbc into swiftlang:main May 13, 2022
@rxwei rxwei deleted the regexparser-no-resilience branch May 13, 2022 19:51
tshortli added a commit to tshortli/swift that referenced this pull request Jan 17, 2024
This was originally attempted with swiftlang#58810
but _RegexParser still ended up being built with library evolution enabled
because the `-enable-library-evolution` flag is added to the command line after
calling `add_swift_target_library` and therefore stripping the flag out of
`SWIFT_COMPILE_FLAGS` does nothing.

Resolves rdar://93067204
tshortli added a commit to tshortli/swift that referenced this pull request Jan 17, 2024
This was originally attempted with swiftlang#58810
but `_RegexParser` still ended up being built with library evolution enabled
because the `-enable-library-evolution` flag is added to the command line after
calling `add_swift_target_library` and therefore stripping the flag out of
`SWIFT_COMPILE_FLAGS` does nothing.

The `IS_FRAGILE` flag was introduced to support building C++ interop overlay
modules without library evolution and it can now be used to prevent
`_RegexParser` from being built with library evolution.

Resolves rdar://93067204
tshortli added a commit to tshortli/swift that referenced this pull request Jan 17, 2024
This was originally attempted with swiftlang#58810
but `_RegexParser` still ended up being built with library evolution enabled
because the `-enable-library-evolution` flag is added to the command line after
calling `add_swift_target_library` and therefore stripping the flag out of
`SWIFT_COMPILE_FLAGS` does nothing.

The `IS_FRAGILE` flag was introduced to support building C++ interop overlay
modules without library evolution and it can now be used to prevent
`_RegexParser` from being built with library evolution.

Resolves rdar://93067204
Catfish-Man pushed a commit to Catfish-Man/swift that referenced this pull request Jan 19, 2024
This was originally attempted with swiftlang#58810
but `_RegexParser` still ended up being built with library evolution enabled
because the `-enable-library-evolution` flag is added to the command line after
calling `add_swift_target_library` and therefore stripping the flag out of
`SWIFT_COMPILE_FLAGS` does nothing.

The `IS_FRAGILE` flag was introduced to support building C++ interop overlay
modules without library evolution and it can now be used to prevent
`_RegexParser` from being built with library evolution.

Resolves rdar://93067204
carlos4242 pushed a commit to carlos4242/swift that referenced this pull request May 31, 2024
This was originally attempted with swiftlang#58810
but `_RegexParser` still ended up being built with library evolution enabled
because the `-enable-library-evolution` flag is added to the command line after
calling `add_swift_target_library` and therefore stripping the flag out of
`SWIFT_COMPILE_FLAGS` does nothing.

The `IS_FRAGILE` flag was introduced to support building C++ interop overlay
modules without library evolution and it can now be used to prevent
`_RegexParser` from being built with library evolution.

Resolves rdar://93067204
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants