Displaying 10 results from an estimated 10 matches for "__deregister_frame".
2010 Sep 22
2
[LLVMdev] Why isn't __deregister_frame called anywhere in LLVM?
...from '_Unwind_Find_registered_FDE'. Crash occurs
on invalid FDE object after several iterations over the valid FDE
objects. So it looks like an invalid FDE object is attached to the valid
ones. Also when I split two JIT runs into the separate processes nothing
crashes.
As I understand, __deregister_frame has to be called during code
removal. I can only see __register_frame call, and not
__deregister_frame. Why?
Yuri
2010 Sep 24
0
[LLVMdev] [PATCH] Why isn't __deregister_frame called anywhere in LLVM?
...ered_FDE'. Crash
> occurs on invalid FDE object after several iterations over the valid
> FDE objects. So it looks like an invalid FDE object is attached to the
> valid ones. Also when I split two JIT runs into the separate processes
> nothing crashes.
>
> As I understand, __deregister_frame has to be called during code
> removal. I can only see __register_frame call, and not
> __deregister_frame. Why?
>
> Yuri
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch.txt
URL: <http://lists.llvm.org/pipermail/llvm-dev...
2013 Jul 30
0
[LLVMdev] LLVM and Cygwin
....cpp:(.text+0x3b):
> undefined reference to `__register_frame'
I register_frame is used to enable the debugger (gdb) to debug JIT'd code. It
is a function provided by libgcc, to be more precise in libgcc_eh. Is it in
your copy?
$ nm libgcc_eh.a | grep register_fram
0000000000001960 T __deregister_frame
0000000000001950 T __deregister_frame_info
0000000000001830 T __deregister_frame_info_bases
0000000000001750 T __register_frame
0000000000001740 T __register_frame_info
00000000000016b0 T __register_frame_info_bases
0000000000001800 T __register_frame_info_table
0000000000001780 T __register_frame_...
2013 Jul 29
5
[LLVMdev] LLVM and Cygwin
I got the following error while compiling llvm and clang under cygwin.
/cygdrive/c/Users/brianherman/Desktop/llvm/llvm-3.3.src/Release+Asserts/lib/libLLVMMCJIT.a(SectionMemoryManager.o):SectionMemoryManager.cpp:(.text+0x3b):
undefined reference to `__register_frame'
2012 Oct 05
0
[LLVMdev] Cross-compiling to x86_64-mingw-w64
...nalysis -lLLVMMCJIT -lLLVMRuntimeDyld
-lLLVMExecutionEngine -lLLVMTarget -lLLVMMC -lLLVMObject -lLLVMCore
-lLLVMSupport -lpthread -lpsapi -limagehlp -lm
/usr/home/solskogen/obj/_build/llvm.native.x86_64-w64-mingw32/Release/lib/libLLVMJIT.a(JIT.o):JIT.cpp:(.text+0x293b):
undefined reference to `__deregister_frame'
/usr/home/solskogen/obj/_build/llvm.native.x86_64-w64-mingw32/Release/lib/libLLVMJIT.a(JIT.o):JIT.cpp:(.text+0x2942):
undefined reference to `__register_frame'
/usr/home/solskogen/obj/cross-mingw-w64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.0/../../../../x86_64-w64-mingw32/bin/ld:
/usr/home...
2013 Jul 30
2
[LLVMdev] LLVM and Cygwin
...gister_frame'
>>
>
> I register_frame is used to enable the debugger (gdb) to debug JIT'd code.
> It
> is a function provided by libgcc, to be more precise in libgcc_eh. Is it
> in
> your copy?
>
> $ nm libgcc_eh.a | grep register_fram
> 0000000000001960 T __deregister_frame
> 0000000000001950 T __deregister_frame_info
> 0000000000001830 T __deregister_frame_info_bases
> 0000000000001750 T __register_frame
> 0000000000001740 T __register_frame_info
> 00000000000016b0 T __register_frame_info_bases
> 0000000000001800 T __register_frame_info_table
> 0...
2020 Aug 15
5
Supporting libunwind on Windows 10 (32bit; 64bit) for MSVC and Clang
...d __register_frame(const void *fde) {
^
C:/Users/clang/libunwind/include\unwind.h:331:13: note: previous
declaration is here
extern void __register_frame(const void *fde);
^
C:/Users/clang/libunwind/src/UnwindLevel1-gcc-ext.c:251:24: warning:
redeclaration of '__deregister_frame' should not add 'dllexport' attribute
[-Wdll-attribute-on-redeclaration]
_LIBUNWIND_EXPORT void __deregister_frame(const void *fde) {
^
C:/Users/clang/libunwind/include\unwind.h:332:13: note: previous
declaration is here
extern void __deregister_frame(const void *...
2017 Jan 23
2
undefined symbols during linking LLDB 4.0 RC1
...0000000077 Base _ZNKSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE7compareEmmPKcm
0000000000000000 DF *UND* 0000000000000040 Base _ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE6resizeEmc
0000000000000000 DF *UND* 0000000000000021 GCC_3.0 __deregister_frame
0000000000000000 DF *UND* 0000000000000005 Base _ZNSt3__118condition_variable10notify_allEv
0000000000000000 DF *UND* 00000000000000fa Base new_panel
0000000000000000 DF *UND* 0000000000000873 GLIBC_2.2.5 setlocale
0000000000000000 DF *UND* 0000000000000009 Bas...
2017 Jan 19
2
undefined symbols during linking LLDB 4.0 RC1
Hello, I update my building scripts to build LLVM 4.0 RC1 (with clang, lldb, libc++, libc++abi, lld) on CentOS 6 and I got a lot of undefined symbols during linking LLDB.
I'm using clang-3.9 and this configuration:
-DLLVM_TARGETS_TO_BUILD="X86"
-DCMAKE_BUILD_TYPE=Release
-DCMAKE_C_COMPILER=/usr/bin/clang
-DCMAKE_CXX_COMPILER=/usr/bin/clang++
2016 Jan 03
4
R, AIX 64-bit builds - trying to understand root cause for message: "Error: Line starting 'Package: tools ...' is malformed!"
On 2016-01-01 23:48, peter dalgaard wrote:
> Nice catch you two!!!
>
> Happy New Year
> -pd
I am much happier with this great start!
Simon - which compiler)s) did you use: xlc and xlfortran, or gcc/gfortran?
I have made some changes to configure(.ac) so maybe my problems are
self-inflicted. But would be good to know what environment you are using.
Thanks for looking - and