[embedded] Ignore 'do not specialize' @_semantics attributes in embedded Swift mode #70810
Conversation
|
@swift-ci please test |
| SubstitutionMap Subs = {}) { | ||
| // Ignore "do not specialize" markers in embedded Swift -- specialization is | ||
| // mandatory. | ||
| if (Callee->getModule().getOptions().EmbeddedSwift) |
There was a problem hiding this comment.
Would be nice if we could do this for perf annotations too, but that's probably a separate patch.
There was a problem hiding this comment.
Hm, I wonder if there is actually anything to fix for perf annotations: (1) The stdlib only has a handful of functions with the "do not specialize" marker and they seem to mostly be slow paths that do cause allocations (and thus are not going to be usable in @noLocks or @noAllocations code anyway). (2) Non-stdlib code probably shouldn't use the "do not specialize" marker as it's an underscored attribute, and arguably it could be considered to be the user's problem if they use the marker and then try to use such a code in a perf-annotated function...
|
@swift-ci please test |
|
@swift-ci please test Windows platform |
3 participants
We cannot allow the 'do not specialize' @_semantics attributes in embedded Swift because specialization is mandatory for soundness of the resulting compilations. The attached test crashes (triggers a "unexpected unspecialized function found during IRGen" assert) without the fix.
We have been a bit lucky that so far the parts of the stdlib that we have for embedded Swift didn't use these attributes, but I have observed that some other parts (e.g. Dictionary implementation) do use them, so we need to fix this problem.