Commit Graph

4 Commits

Author SHA1 Message Date
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
Pavel Yaskevich
1e9e351a3f [SILGen] Fix any Sendable to Any bridging when result should be placed in a buffer
If the context indicates that the result of `id-to-Any` should be
placed in some pre-allocated buffer, let's not attempt marker existential
transformation because that would much the expected layout already.
2024-06-17 09:45:00 -07:00
Holly Borla
d3c42649b7 [SILGen] Handle marker existentials in emitCBridgedToNativeValue. 2023-12-19 19:02:21 -08:00
Slava Pestov
385a7beb45 SIL: Bridge 'any Sendable' via the id-as-Any path
Fixes rdar://problem/107264240.
2023-04-25 13:53:11 -04:00