Commit Graph

3 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
Anthony Latsis
a68b5545e2 Gardening: Migrate test suite to GH issues: SIL 2022-09-04 07:02:59 +03:00
Min-Yih Hsu
007ec33d48 [SIL] Fix incorrect handling of 'forwarding' when parsing SIL
The `forwarding` directive should be optional for SIL instructions.
However, the current SIL parser put it as a requirement when there is a
comma follows after the main instruction components, which conflicts
with debug info directives like `loc` or `scope`. This patch teaches the
parser to treat `forwarding` as an optional directive.

Resolves SR-14814.
2021-06-24 09:54:22 -07:00