Displaying 5 results from an estimated 5 matches for "_return_path".
Did you mean:
return_path
2013 Nov 09
4
[LLVMdev] Error "Cannot emit physreg copy instruction"
...ethrow(i8*)
; Function Attrs: uwtable
define internal void @_release_Au32a(i8**) #0 {
entry:
ret void
}
; Function Attrs: uwtable
define internal void @_release_C0PpRbrc(%0**) #0 {
entry:
ret void
}
; Function Attrs: uwtable
define internal i8* @junk___init_module_get_args_3() #0 {
entry:
%_return_path = alloca i8
store i8 0, i8* %_return_path
%_exception = alloca { i8*, i64 }
%_return_val = alloca i8*
%junk__a = alloca %junk__range_iter
%cond_result = alloca i1
%0 = call i8* @count_malloc(i64 16)
%1 = bitcast i8* %0 to i64*
store i64 0, i64* %1
store i8* %0, i8** %_return_val...
2013 Apr 11
0
[LLVMdev] object file/linking is missing my exception handlers
Hi,
On 11/04/13 06:06, edA-qa mort-ora-y wrote:
> I have some exception handling which works fine using the JIT. Now I am
> producing object files and linking them, but the exception handling
> tables seem to be missing. I call _Unwind_RaiseException and get
> _URC_END_OF_STACK as a result.
you will get this if no catch clauses match (eg because there are no catch
clauses, perhaps
2013 Apr 11
4
[LLVMdev] object file/linking is missing my exception handlers
I have some exception handling which works fine using the JIT. Now I am
producing object files and linking them, but the exception handling
tables seem to be missing. I call _Unwind_RaiseException and get
_URC_END_OF_STACK as a result.
I produce my object file using TargetMachine::addPassesToEmitFile and
then I link my resulting files with:
gcc -o prog input.o -fexceptions
I'm sure I'm
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