Displaying 3 results from an estimated 3 matches for "d8aa07f3".
Did you mean:
d8a207fb
2010 Sep 26
0
[LLVMdev] LLVM Exception Handling
On 26 September 2010 20:13, Nathan Jeffords <blunted2night at gmail.com> wrote:
> I believe the perceived problem with using eh.exception is that
> is disassociates the source of the value with the invoke instruction that
> generated it. As far as reusing the landing pad, that is still possible, it
> would just require a phi node in the landing pad to bring all the different
>
2010 Sep 26
2
[LLVMdev] LLVM Exception Handling
...stemcall.org/
>
> Reclaim your digital rights, eliminate DRM, learn more at
> http://www.defectivebydesign.org/what_is_drm
>
thanks,
-Nathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100926/d8aa07f3/attachment.html>
2010 Sep 26
3
[LLVMdev] LLVM Exception Handling
On Sun, Sep 26, 2010 at 11:27 AM, Renato Golin <rengolin at systemcall.org>wrote:
> On 26 September 2010 18:56, Nathan Jeffords <blunted2night at gmail.com>
> wrote:
> > The syntax for the invoke instruction is a little misleading. %x is a
> value
> > that is being generated by the instruction, not passed to is. It is no
> > different in that regard as to