Displaying 4 results from an estimated 4 matches for "_raise_exception".
Did you mean:
raise_exception
2014 Apr 17
2
[LLVMdev] [PATCH] Seh exceptions on Win64
Hi,
On 15.04.2014 23:44, Vadim Chugunov wrote:
> Hi,
> I am curious - how does clang deal with epilogue-less functions that
> result from _Raise_Exception being marked 'noreturn'?
> I've also been playing with Kai's patch, and discovered that this tends
> to greatly confuse Windows stack unwinder in cases when noreturn call is
> at the end of a function, so execution appears to flow directly into the
> prologue of the next...
2014 Apr 15
10
[LLVMdev] [PATCH] Seh exceptions on Win64
Hi,
I'd like to submit a patch to match the clang patch on the front end.
http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20140414/103257.html
The front end doesn't need this patch to work but it's still important.
This is mostly based on work done by kai from redstar.de
Could I get some feedback on this?
I'm not sure if the emitting of the register names will effect
2013 Oct 18
0
[LLVMdev] post-link Dwarf information appears wrong, works in JIT
On Oct 17, 2013, at 7:24 PM, edA-qa mort-ora-y <eda-qa at disemia.com> wrote:
> On 17/10/13 23:57, Bill Wendling wrote:
>> There shouldn't be any special linker flags you need to use. If
>> you're getting segfaults, it's probably trying to access the data at
>> an invalid location or something. Make sure that your EH table is
>> properly aligned. You
2013 Oct 18
2
[LLVMdev] post-link Dwarf information appears wrong, works in JIT
On 17/10/13 23:57, Bill Wendling wrote:
> There shouldn't be any special linker flags you need to use. If
> you're getting segfaults, it's probably trying to access the data at
> an invalid location or something. Make sure that your EH table is
> properly aligned. You might want to hand calculate the values to make
> sure that they're correct. What platform are you