5 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
Holly Borla	8713d78704	[PrintOptions] Print explicit 'any' in SIL.	2022-08-18 01:15:12 -04:00
Slava Pestov	a2dbdecdab	SIL: Refactor get_async_continuation[_addr] to return a RawUnsafeContinuation	2020-12-01 20:04:09 -05:00
Meghana Gupta	288ef583e7	SILVerifier: async functions can be called from async functions only	2020-10-30 17:35:18 -07:00
Joe Groff	a664a33b52	SIL: Add instructions to represent async suspend points. ... `get_async_continuation[_addr]` begins a suspend operation by accessing the continuation value that can resume the task, which can then be used in a callback or event handler before executing `await_async_continuation` to suspend the task.	2020-10-01 14:21:52 -07:00