search for: tongari

2017-06-02 19:51 GMT+08:00 David Chisnall <David.Chisnall at cl.cam.ac.uk>: > On 2 Jun 2017, at 03:38, TONGARI J via llvm-dev <llvm-dev at lists.llvm.org> > wrote: > > > > I'm aware of the invoke instruction and landingpad. But it's too heavy > > weight for control flow. It's quite expensive to take the exceptional > path > > in C++. > > > > What I...

Hi Reid, I'm aware of the invoke instruction and landingpad. But it's too heavy weight for control flow. It's quite expensive to take the exceptional path in C++. What I want is a more lightweight approach, to pass the return address to the callee, and let the callee jump to that address directly. -------------- next part -------------- An HTML attachment was scrubbed... URL:

2017-06-07 22:51 GMT+08:00 David Chisnall <David.Chisnall at cl.cam.ac.uk>: > > You could approximate this using the address-of-label extension and > passing the address of the return basic block to the function then, in the > abnormal return path, jumping to that. Doing anything else is likely to be > very complicated because the live registers at all of the potential

Hi folks, I'm new to LLVM and non-expert in hardware architecture, so my question might be dumb. I'm looking for the possibility to define/call a function with multi return path, it might look like this: ``` ; Define a function with 1 alternate return path define i32 @f(i1 %i) fork 1 { br i1 %i, label %noraml, label %alternate noraml: ... setpath ret i32 42 ; take normal return