search for: endfunct

...he module > cmake/Modules/CompilerRTUtils.cmake: > > function(set_target_compile_flags target) > foreach(arg ${ARGN}) > set(argstring "${argstring} ${arg}") > endforeach() > set_property(TARGET ${target} PROPERTY COMPILE_FLAGS "${argstring}") > endfunction() > > but that makes no attempt to escape or quote anything. > > The COMPILE_FLAGS target property was a very early CMake feature > and is treated as a raw string to put on the command line. That > is why it needs manual escaping. > > CMake 2.8.12 added the COMPILE_OP...

...d that generates LLVM debug info metadata. I was using LLVM 2.9 debug version and I'm moving to LLVM 3.2 debug version of metadata. On my example I got llc 3.2 to fail on following assertion: llc: /work1/tools/llvm/3.2/sources/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1471: void llvm::DwarfDebug::endFunction(const llvm::MachineFunction*): Assertion `TheCU && "Unable to find compile unit!"' failed. 0 llc 0x0000000000ffb43f 1 llc 0x0000000000ffd6ba 2 libpthread.so.0 0x00007f5dd70238f0 3 libc.so.6 0x00007f5dd6312a75 gsignal + 53 4 libc.so.6...

...gr->endExceptionTable(F.getFunction(), BufferBegin, > CurBufferPtr, FrameRegister); > + BufferBegin = SavedBufferBegin; > + BufferEnd = SavedBufferEnd; > + CurBufferPtr = SavedCurBufferPtr; > + > + TheJIT->RegisterTable(FrameRegister); > + } > + MMI->EndFunction(); > + > return false; > } > > Index: lib/ExecutionEngine/JIT/JITMemoryManager.cpp > =================================================================== > --- lib/ExecutionEngine/JIT/JITMemoryManager.cpp (revision 46612) > +++ lib/ExecutionEngine/JIT/JITMemoryManager.cp...

Dear all, Here's a new patch with Evan's comments (thx Evan!) and some cleanups. Now the (duplicated) exception handling code is in a new file: lib/ExecutionEngine/JIT/JITDwarfEmitter. This patch should work on linux/x86 and linux/ppc (tested). Nicolas -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: jit-exceptions.patch URL:

...tRegisterInfo(); > + MemMgr = JITMemoryManager::CreateDefaultMemManager(); > + } > + > + unsigned char* EmitExceptionTable(MachineFunction* MF, > + unsigned char* StartFunction, > + unsigned char* EndFunction); > + > + void EmitFrameMoves(intptr_t BaseLabelPtr, > + const std::vector<MachineMove> &Moves); > + > + unsigned char* EmitCommonEHFrame(const Function* Personality); > + > + unsigned char* EmitEHFrame(const Function* Personality, &...

Hi everyone, Here's a patch that enables exception handling when jitting. I've copy/pasted _many_code from lib/Codegen/DwarfWriter.cpp, so we may need to factorize it, but the functionality is there and I'm very happy with it :) lli should now be able to execute the output from llvm-gcc when using exceptions (the UnwindInst instruction is not involved in this patch). Just add the

...ated memory? > If I understand correctly the numbers, this does not tell anything about how much the Dwarf emitter accounts on the *peak memory* usage (could be more, could be nothing...). I think these nodes represent allocations from the DWARF emitter: DwarfDebug::DwarfDebug 9.5% DwarfDebug::endFunction 15.6% DIEValueList::addValue 9.1% total 34.2% I believe they are totals, but my reading of the code is that the DWARF emitter does not deallocate its memory until the end of code generation, so total ~= peak in this case. I am not surprised by these figures -- see e.g. DIEValueList::Node which...

...; + MemMgr = JITMemoryManager::CreateDefaultMemManager(); >> + } >> + >> + unsigned char* EmitExceptionTable(MachineFunction* MF, >> + unsigned char* StartFunction, >> + unsigned char* EndFunction); >> + >> + void EmitFrameMoves(intptr_t BaseLabelPtr, >> + const std::vector<MachineMove> &Moves); >> + >> + unsigned char* EmitCommonEHFrame(const Function* Personality); >> + >> + unsigned char* EmitEHFrame(co...

So, I just sync'd to LLVM tip and added the call to DIBuilder::finalize(). But even with that change I am getting an error when I try to run llc: Assertion failed: (TheCU && "Unable to find compile unit!"), function endFunction, file /Users/talin/Projects/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line 1306. And looking at the .bc dissassembly, I see there are indeed compile unit MDNodes, although at this level I can't tell if they are hooked up correctly. On Wed, Aug 31, 2011 at 9:07 AM, Devang Patel <dpatel...

...his does not tell anything > about how much the Dwarf emitter accounts on the *peak memory* usage (could > be more, could be nothing...). > > > > I think these nodes represent allocations from the DWARF emitter: > > > > DwarfDebug::DwarfDebug 9.5% > > DwarfDebug::endFunction 15.6% > > DIEValueList::addValue 9.1% > > total 34.2% > > > > I believe they are totals, but my reading of the code is that the DWARF > > emitter does not deallocate its memory until the end of code generation, > > That's sad :( > > > so total ~=...

...ta schema by modifying DIBuilder without concern for other clients creating debug info metadata separately. - David > On my example I got llc 3.2 to fail on following assertion: > > > llc: /work1/tools/llvm/3.2/sources/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1471: void llvm::DwarfDebug::endFunction(const llvm::MachineFunction*): Assertion `TheCU && "Unable to find compile unit!"' failed. > 0 llc 0x0000000000ffb43f > 1 llc 0x0000000000ffd6ba > 2 libpthread.so.0 0x00007f5dd70238f0 > 3 libc.so.6 0x00007f5dd6312a75 gsignal + 5...

Thx again Evan for the review. Here's a new patch for the JIT in itself. The major changes are: 1) A JITMemoryManager now has a flag saying "I require to know the size of what you want to emit" 2) DwarfJITEmitter is augmented with GetSize* functions 3) JITEmitter::startFunction checks if the JITMemoryManager requires to know the size. If so, it computes it and gives it through the

...llvm::WinEHFuncInfo const &) c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:320:0 ; #2 0x00f97f75 llvm::WinException::emitCXXFrameHandler3Table(class llvm::MachineFunction const *,bool) c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:805:0 ; #3 0x00f98e77 llvm::WinException::endFunction(class llvm::MachineFunction const *) c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:146:0 ; #4 0x00f685f7 llvm::AsmPrinter::EmitFunctionBody(void) c:\p\llvm\llvm\lib\codegen\asmprinter\asmprinter.cpp:978:0 ; #5 0x00d307fa llvm::X86AsmPrinter::runOnMachineFunction(class llvm::MachineF...

..., > > > So, I just sync'd to LLVM tip and added the call to > DIBuilder::finalize(). But > > even with that change I am getting an error when I try to run llc: > > > > Assertion failed: (TheCU && "Unable to find compile unit!"), function > > endFunction, file > > /Users/talin/Projects/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line > 1306. > > > > And looking at the .bc dissassembly, I see there are indeed compile unit > > MDNodes, although at this level I can't tell if they are hooked up > correctly. > &gt...

A couple of llvm sub-projects have been failing to build for me for a while (compiler-rt asan and util/unittests, at least). It turns out to be due to the fact that some paths on my system include spaces and other special characters, but the the build.ninja file was not generated with correctly quoted strings. Specifically I'm on OS X and the command is setting -isysroot to a location inside

...============================================================================== > --- compiler-rt/trunk/lib/xray/tests/CMakeLists.txt (original) > +++ compiler-rt/trunk/lib/xray/tests/CMakeLists.txt Tue Apr 10 22:16:11 2018 > @@ -34,13 +34,18 @@ function(get_xray_lib_for_arch arch lib) > endfunction() > > set(XRAY_TEST_ARCH ${XRAY_SUPPORTED_ARCH}) > +set(XRAY_UNITTEST_LINK_FLAGS ${CMAKE_THREAD_LIBS_INIT}) > +if (NOT APPLE) > + append_list_if(COMPILER_RT_HAS_LIBM -lm XRAY_UNITTEST_LINK_FLAGS) > + append_list_if(COMPILER_RT_HAS_LIBRT -lrt XRAY_UNITTEST_LINK_FLAGS) > +...

Hi Talin, > So, I just sync'd to LLVM tip and added the call to DIBuilder::finalize(). But > even with that change I am getting an error when I try to run llc: > > Assertion failed: (TheCU && "Unable to find compile unit!"), function > endFunction, file > /Users/talin/Projects/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line 1306. > > And looking at the .bc dissassembly, I see there are indeed compile unit > MDNodes, although at this level I can't tell if they are hooked up correctly. you might want to take a look at this...

...; c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:320:0 >> ; #2 0x00f97f75 llvm::WinException::emitCXXFrameHandler3Table(class >> llvm::MachineFunction const *,bool) >> c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:805:0 >> ; #3 0x00f98e77 llvm::WinException::endFunction(class >> llvm::MachineFunction const *) >> c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:146:0 >> ; #4 0x00f685f7 llvm::AsmPrinter::EmitFunctionBody(void) >> c:\p\llvm\llvm\lib\codegen\asmprinter\asmprinter.cpp:978:0 >> ; #5 0x00d307fa llvm::X86AsmPrinter::...

...ke b/cmake/modules/TableGen.cmake > index 452a728..cb06450 100644 > --- a/cmake/modules/TableGen.cmake > +++ b/cmake/modules/TableGen.cmake > @@ -70,6 +70,15 @@ function(add_public_tablegen_target target) > set(LLVM_COMMON_DEPENDS ${LLVM_COMMON_DEPENDS} ${target} PARENT_SCOPE) > endfunction() > > +if(LLVM_USE_HOST_TOOLS) > + add_custom_command(OUTPUT LIB_LLVMSUPPORT > + COMMAND ${CMAKE_COMMAND} --build . --target LLVMSupport --config Release > + DEPENDS CONFIGURE_LLVM_NATIVE > + WORKING_DIRECTORY ${LLVM_NATIVE_BUILD} > + COMMENT "Buil...

...d185aa _sigtramp + 26 > 3 libsystem_platform.dylib 000000000000000000 _sigtramp + 1915648624 > 4 clang-3.4 0x0000000103ff3ac6 abort + 22 > 5 clang-3.4 0x0000000103ff3aa1 __assert_rtn + 81 > 6 clang-3.4 0x00000001038bcb70 llvm::DwarfDebug::endFunction(llvm::MachineFunction const*) + 0 > 7 clang-3.4 0x0000000103892677 llvm::AsmPrinter::EmitFunctionHeader() + 727 > 8 clang-3.4 0x00000001036229ea llvm::X86AsmPrinter::runOnMachineFunction(llvm::MachineFunction&) + 170 > 9 clang-3.4 0x00...