5 Commits

Author	SHA1	Message	Date
Mykola Pokhylets	89f8f8b9bf	Wrap only changes related to the closure frontend logic	2025-08-02 20:24:46 +02:00
Mykola Pokhylets	ae48446716	Wrap SE-0481 into an upcoming feature until source incompatibilities are resolved	2025-08-02 20:24:21 +02:00
Mykola Pokhylets	04166e21c9	Fixed some tests ... Remaining failures: SILGen/unowned-class-bound-generic-parameter.swift	2025-05-19 17:03:59 +02:00
Erik Eckstein	7cceaff5f3	SIL: don't print operand types in textual SIL ... Type annotations for instruction operands are omitted, e.g. ``` %3 = struct $S(%1, %2) ``` Operand types are redundant anyway and were only used for sanity checking in the SIL parser. But: operand types _are_ printed if the definition of the operand value was not printed yet. This happens: * if the block with the definition appears after the block where the operand's instruction is located * if a block or instruction is printed in isolation, e.g. in a debugger The old behavior can be restored with `-Xllvm -sil-print-types`. This option is added to many existing test files which check for operand types in their check-lines.	2024-11-21 18:49:52 +01:00
Adrian Prantl	329e42849a	Compute VarDeclScopeMap up front. ... The previous lazy discovery did not always work because sometimes a debug_value is emitted before the first SIL instruction in the variable's scope. rdar://110841130	2023-06-16 14:32:30 -07:00