mirror of
https://github.com/apple/swift.git
synced 2025-12-21 12:14:44 +01:00
Fix EscapeAnalysis value_to_bridge_object and strong_copy_unowned_value.
Noticed via code inspection. This could potentially miscompile, but we haven't seen that happen to my knowledge. Both value_to_bridge_object and strong_copy_XXX need to escape their resulting value. The implementation seemed to assume that it is conservatively correct simply to avoid building a connection graph node for an value. This is *not* true. Any value that has a pointer type requires a connection graph node. The only way to be conservative is to create the value node *and* point it to an escaping content node. We can always declare that certain special types are not considered pointer types, but then we need to handle all conversions from those types to pointer types by escaping the resulting pointer. BridgeObjects are often on the performance-critical path.
This commit is contained in:
@@ -2020,12 +2020,9 @@ void EscapeAnalysis::analyzeInstruction(SILInstruction *I,
|
||||
ConGraph->getNode(cast<SingleValueInstruction>(I));
|
||||
return;
|
||||
|
||||
#define UNCHECKED_REF_STORAGE(Name, ...) \
|
||||
case SILInstructionKind::StrongCopy##Name##ValueInst:
|
||||
#define ALWAYS_OR_SOMETIMES_LOADABLE_CHECKED_REF_STORAGE(Name, ...) \
|
||||
case SILInstructionKind::Name##RetainInst: \
|
||||
case SILInstructionKind::StrongRetain##Name##Inst: \
|
||||
case SILInstructionKind::StrongCopy##Name##ValueInst:
|
||||
case SILInstructionKind::StrongRetain##Name##Inst:
|
||||
#include "swift/AST/ReferenceStorage.def"
|
||||
case SILInstructionKind::DeallocStackInst:
|
||||
case SILInstructionKind::StrongRetainInst:
|
||||
@@ -2043,8 +2040,11 @@ void EscapeAnalysis::analyzeInstruction(SILInstruction *I,
|
||||
case SILInstructionKind::SetDeallocatingInst:
|
||||
case SILInstructionKind::FixLifetimeInst:
|
||||
case SILInstructionKind::ClassifyBridgeObjectInst:
|
||||
case SILInstructionKind::ValueToBridgeObjectInst:
|
||||
// These instructions don't have any effect on escaping.
|
||||
// Early bailout: These instructions never produce a pointer value and
|
||||
// have no escaping effect on their operands.
|
||||
assert(!llvm::any_of(I->getResults(), [this](SILValue result) {
|
||||
return isPointer(result);
|
||||
}));
|
||||
return;
|
||||
|
||||
#define ALWAYS_OR_SOMETIMES_LOADABLE_CHECKED_REF_STORAGE(Name, ...) \
|
||||
|
||||
Reference in New Issue
Block a user