Don't treat dependent types as having a copy value representation. (#6055)

Add `Dependent` value and initializing representations for types whose
representations are unknown because they are dependent. When generating
SemIR in such cases, use a worst-case initializing representation that
both provides a destination address and also propagates a potential
result value.

Use this to fix incorrect lowering and lowering crashes for specific
functions involving generic types that don't use a copy value
representation.

In lowering, be careful to distinguish between whether the initializing
representation for the generic return type uses a return slot (which
affects whether the SemIR declaration and call have one) and whether the
initializing representation for the specific return type uses a return
slot (which affects whether the LLVM IR declaration and call have one).
This commit is contained in:
Richard Smith
2025-09-15 23:59:00 +00:00
committed by GitHub
parent ca40e9d693
commit b44ba47cf3
53 changed files with 1375 additions and 670 deletions
+5
View File
@@ -285,6 +285,9 @@ auto FunctionContext::FinishInit(TypeInFile type, SemIR::InstId dest_id,
case SemIR::InitRepr::Incomplete:
CARBON_FATAL("Lowering aggregate initialization of incomplete type {0}",
type.file->types().GetAsInst(type.type_id));
case SemIR::InitRepr::Dependent:
CARBON_FATAL("Lowering aggregate initialization of dependent type {0}",
type.file->types().GetAsInst(type.type_id));
}
}
@@ -368,6 +371,8 @@ auto FunctionContext::CopyValue(TypeInFile type, SemIR::InstId source_id,
switch (GetValueRepr(type).repr.kind) {
case SemIR::ValueRepr::Unknown:
CARBON_FATAL("Attempt to copy incomplete type");
case SemIR::ValueRepr::Dependent:
CARBON_FATAL("Attempt to copy dependent type");
case SemIR::ValueRepr::None:
break;
case SemIR::ValueRepr::Copy: