Displaying 10 results from an estimated 10 matches for "gctool".
Did you mean:
gctools
2017 Apr 24
3
Debugging UNREACHABLE "Couldn't join subrange" in RegisterCoalescer (out-of-tree backend)
...112r 1 at 96r L00000030 [208r,288r:1) 0 at x 1 at 208r L00000001 [96r,288r:0) 0 at 96r
Copy+Merge 00000030 into 00000020
Reduce Lane to 00000010
conflict at %vreg34:1 at 240r
*** Couldn't join subrange!
UNREACHABLE executed at /d/en/johnsoni-0/gctools/llvm/lib/CodeGen/RegisterCoalescer.cpp:2693!
#0 0x00000000027395af llvm::sys::PrintStackTrace(llvm::raw_ostream&) /d/en/johnsoni-0/gctools/llvm/lib/Support/Unix/Signals.inc:402:0
#1 0x0000000002739971 PrintStackTraceSignalHandler(void*) /d/en/johnsoni-0/gctools/llvm/lib/Support/Unix/Signals.in...
2015 Jan 17
2
[LLVMdev] Assertion: replaceAllUses of value with new value of different type! being thrown all of a sudden
...::finalize(this=0x0000000116bba4e0) + 185 at DIBuilder.cpp:40
frame #8: 0x00000001010cd4c8 clasp_boehm_d`core::IndirectVariadicMethoid<core::policies::policies_<>, llvmo::DIBuilder_O, void (this=0x000000010c6ea5b8, lcc_resultP=0x00007fff5fb9eb58, arg0=<unavailable>)()>::invoke(gctools::multiple_values<core::T_O>*, gctools::smart_ptr<core::T_O>) + 232 at external_wrappers_indirect_methoids.h:2704
frame #9: 0x00000001010cd1f1 clasp_boehm_d`core::IndirectVariadicMethoid<core::policies::policies_<>, llvmo::DIBuilder_O, void (this=0x000000010c6ea5b8, lcc_res...
2015 Jan 19
2
[LLVMdev] Assertion: replaceAllUses of value with new value of different type! being thrown all of a sudden
...ize(this=0x0000000116bba4e0) + 185 at DIBuilder.cpp:40
>> frame #8: 0x00000001010cd4c8 clasp_boehm_d`core::IndirectVariadicMethoid<core::policies::policies_<>, llvmo::DIBuilder_O, void (this=0x000000010c6ea5b8, lcc_resultP=0x00007fff5fb9eb58, arg0=<unavailable>)()>::invoke(gctools::multiple_values<core::T_O>*, gctools::smart_ptr<core::T_O>) + 232 at external_wrappers_indirect_methoids.h:2704
>> frame #9: 0x00000001010cd1f1 clasp_boehm_d`core::IndirectVariadicMethoid<core::policies::policies_<>, llvmo::DIBuilder_O, void (this=0x000000010c6ea5b8,...
2015 Apr 09
3
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
...t;(TRY-0).handler-block14470", label %"(TRY-0).dispatch-header19", !dbg !26
I’m getting this error when I throw a core::Unwind exception and I’m certain that there is a landing pad with that clause.
libc++abi.dylib: terminating with uncaught exception of type core::Unwind
../../src/gctools/memoryManagement.cc:75 Trapped SIGABRT - starting debugger
ABORT was called!!!!!!!!!!!!
I’ve written a Common Lisp compiler that uses LLVM as the backend and it interoperates with C++ code and I use C++ exception handling for non-local exits.
-------------- next part --------------
An HTML attac...
2015 Apr 09
2
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
...-0).dispatch-header19", !dbg !26
>
>
>
> I’m getting this error when I throw a core::Unwind exception and I’m
> certain that there is a landing pad with that clause.
>
>
>
> libc++abi.dylib: terminating with uncaught exception of type core::Unwind
>
> ../../src/gctools/memoryManagement.cc:75 Trapped SIGABRT - starting
> debugger
>
> ABORT was called!!!!!!!!!!!!
>
>
>
>
>
> I’ve written a Common Lisp compiler that uses LLVM as the backend and it
> interoperates with C++ code and I use C++ exception handling for non-local
> exits....
2015 Apr 12
2
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
...t;
>>
>>
>> I’m getting this error when I throw a core::Unwind exception and I’m
>> certain that there is a landing pad with that clause.
>>
>>
>>
>> libc++abi.dylib: terminating with uncaught exception of type core::Unwind
>>
>> ../../src/gctools/memoryManagement.cc <http://memorymanagement.cc/>:75
>> Trapped SIGABRT - starting debugger
>>
>> ABORT was called!!!!!!!!!!!!
>>
>>
>>
>>
>>
>> I’ve written a Common Lisp compiler that uses LLVM as the backend and it
>> interoperat...
2015 Apr 12
2
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
...; I’m getting this error when I throw a core::Unwind exception and I’m
>>> certain that there is a landing pad with that clause.
>>>
>>>
>>>
>>> libc++abi.dylib: terminating with uncaught exception of type core::Unwind
>>>
>>> ../../src/gctools/memoryManagement.cc <http://memorymanagement.cc/>:75
>>> Trapped SIGABRT - starting debugger
>>>
>>> ABORT was called!!!!!!!!!!!!
>>>
>>>
>>>
>>>
>>>
>>> I’ve written a Common Lisp compiler that uses LLVM as the...
2015 Apr 12
2
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
...is error when I throw a core::Unwind exception and I’m certain that there is a landing pad with that clause.
>>>>
>>>>
>>>>
>>>> libc++abi.dylib: terminating with uncaught exception of type core::Unwind
>>>>
>>>> ../../src/gctools/memoryManagement.cc:75 Trapped SIGABRT - starting debugger
>>>>
>>>> ABORT was called!!!!!!!!!!!!
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> I’ve written a Common Lisp compiler that uses LLVM as the backend...
2015 Apr 12
2
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
...nd I’m certain that there is a landing pad with that clause.
>>>>>>
>>>>>>
>>>>>>
>>>>>> libc++abi.dylib: terminating with uncaught exception of type core::Unwind
>>>>>>
>>>>>> ../../src/gctools/memoryManagement.cc:75 Trapped SIGABRT - starting debugger
>>>>>>
>>>>>> ABORT was called!!!!!!!!!!!!
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> I’...
2015 Apr 12
2
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
...e is a landing pad with that clause.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> libc++abi.dylib: terminating with uncaught exception of type core::Unwind
>>>>>>>
>>>>>>> ../../src/gctools/memoryManagement.cc:75 Trapped SIGABRT - starting debugger
>>>>>>>
>>>>>>> ABORT was called!!!!!!!!!!!!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>...