search for: suspend1

...f this thread. Thank you for being patient with me. Two questions and one clarification: Q1: Do we have to have a load here? =================================== >> block1: >> %first_time = load... <--- What are we loading here? >> br i1 %first_time, label return, label suspend1 >> >> supend1: >> %0 = coro.suspend() >> switch %0 (resume1, destroy1) Can we use three way coro.suspend instead? Block1: %0 = call i8 coro.suspend() switch i8 %0, label suspend1 [i8 0 %return] ; or icmp + br i1 Suspend1: switch i8 %0, label %resume1...

On Fri, Jun 10, 2016 at 5:25 PM, Gor Nishanov <gornishanov at gmail.com> wrote: > Hi Eli: > > >> Naively, you would expect that it would be legal to hoist the store... > >> but that breaks your coroutine semantics because the global could be > mutated > >> between the first return and the resume. > > Hmmm... I don't see the problem. I think

Hi Eli: >> Block1: >> %0 = call i8 coro.suspend() >> switch i8 %0, label suspend1 [i8 0 %return] ; or icmp + br i1 >> Suspend1: >> switch i8 %0, label %resume1 [i8 1 %destroy1] ; or icmp + br i1 >> >> This doesn't look right: intuitively the suspend happens after the return >> block runs. Perhaps, but, that is not the intended semantics....