Skip to content

SIL: Fix recent bug introduced into old style mangling of specializations #7993

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

Conversation

slavapestov
Copy link
Contributor

The format is "type conformances... '_'" for each substitutable
generic parameter. I broke it so that it emits types for the
substitutable parameters but conformances for all requirements
in the signature.

This changed the mangling of specializations where the function
being specialized placed additional constraints on associated
types, causing demangling failure in the pre-specialization
whitelist code.

This might fix rdar://problem/30932656.

…ions

The format is "type conformances... '_'" for each substitutable
generic parameter. I broke it so that it emits types for the
substitutable parameters but conformances for all requirements
in the signature.

This changed the mangling of specializations where the function
being specialized placed additional constraints on associated
types, causing demangling failure in the pre-specialization
whitelist code.

This might fix <rdar://problem/30932656>.
@slavapestov
Copy link
Contributor Author

No test because the old mangling is going away, and new mangling has its own issues (it doesn't mangle conformances in substitutions, which is wrong for property behaviors and private conformances).

@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test

@slavapestov
Copy link
Contributor Author

@swiftix Please review

@swiftix
Copy link
Contributor

swiftix commented Mar 9, 2017

@slavapestov Looks good! I checked locally that it fixes the performance regression.

@slavapestov slavapestov merged commit c082096 into swiftlang:master Mar 9, 2017
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