search for: emitfunctionbody

Hi Violeta, I compiled with clang -Oz and clang -Oz -mno-red-zone for comparisons against Oz and clang -O0 and clang -O0 -mno-red-zone for comparisons against a default clang. I unfortunately don’t have the clang commit I worked with on my home laptop, and don’t have access to the computer I was using at Apple, so I can’t help you there. Jessica > On Sep 28, 2016, at 11:22 AM, Violeta

...e value of putting them in a readonly data section in the non-PIC case. Would it be a problem if they were always in the function code section? (And for dead-stripping purposes, they should be within the bounds of the function symbol, so they need to be emitted a little earlier within AsmPrinter::EmitFunctionBody(). No point in having the jump tables be their own atom, I think.) --paulr

...x00007f5dd6312a75 gsignal + 53 4 libc.so.6 0x00007f5dd63165c0 abort + 384 5 libc.so.6 0x00007f5dd630b941 __assert_fail + 241 6 llc 0x0000000000b22f20 llvm::DwarfDebug::endFunction(llvm::MachineFunction const*) + 3232 7 llc 0x0000000000b0ea9b llvm::AsmPrinter::EmitFunctionBody() + 3291 8 llc 0x0000000000895f1d 9 llc 0x0000000000f995cd llvm::FPPassManager::runOnFunction(llvm::Function&) + 557 10 llc 0x0000000000f996b3 llvm::FPPassManager::runOnModule(llvm::Module&) + 51 11 llc 0x0000000000f99141 llvm::MPPassManager...

...andler3Table(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::MachineFunction &) c:\p\llvm\llvm\lib\target\x86\x86asmprinter.cpp:73:0 ; #6 0x01021d1b llvm::MachineFunctionPass::runOnFunction(class llvm::Function &)...

...5:5 #12 0x00000000007a036b llvm::X86AsmPrinter::EmitAndCountInstruction(llvm::MCInst&) lib/Target/X86/X86MCInstLower.cpp:106:3 #13 0x00000000007a32dc llvm::X86AsmPrinter::EmitInstruction(llvm::MachineInstr const*) lib/Target/X86/X86MCInstLower.cpp:1849:1 #14 0x0000000000dde226 llvm::AsmPrinter::EmitFunctionBody() lib/CodeGen/AsmPrinter/AsmPrinter.cpp:943:11 #15 0x0000000000796e81 llvm::X86AsmPrinter::runOnMachineFunction(llvm::MachineFunction&) lib/Target/X86/X86AsmPrinter.cpp:73:3 #16 0x000000000104d441 llvm::MachineFunctionPass::runOnFunction(llvm::Function&) lib/CodeGen/MachineFunctionPass.cpp:...

...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::MachineFunction &) >> c:\p\llvm\llvm\lib\target\x86\x86asmprinter.cpp:73:0 >> ; #6 0x01021d1b llvm::MachineFunctionPass::...

...ruction(llvm::MCInst&) /home/shenyouren/workspace/llvm/lib/Target/X86/X86MCInstLower.cpp:107:0 #17 0x0000000002360ae9 llvm::X86AsmPrinter::EmitInstruction(llvm::MachineInstr const*) /home/shenyouren/workspace/llvm/lib/Target/X86/X86MCInstLower.cpp:2604:0 #18 0x000000000292e629 llvm::AsmPrinter::EmitFunctionBody() /home/shenyouren/workspace/llvm/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:1086:0 #19 0x0000000002352908 llvm::X86AsmPrinter::runOnMachineFunction(llvm::MachineFunction&) /home/shenyouren/workspace/llvm/lib/Target/X86/X86AsmPrinter.cpp:79:0 #20 0x0000000002bc6afa llvm::MachineFunctionPass::runOnFu...

...ignal + 53 > 4 libc.so.6 0x00007f5dd63165c0 abort + 384 > 5 libc.so.6 0x00007f5dd630b941 __assert_fail + 241 > 6 llc 0x0000000000b22f20 llvm::DwarfDebug::endFunction(llvm::MachineFunction const*) + 3232 > 7 llc 0x0000000000b0ea9b llvm::AsmPrinter::EmitFunctionBody() + 3291 > 8 llc 0x0000000000895f1d > 9 llc 0x0000000000f995cd llvm::FPPassManager::runOnFunction(llvm::Function&) + 557 > 10 llc 0x0000000000f996b3 llvm::FPPassManager::runOnModule(llvm::Module&) + 51 > 11 llc 0x0000000000f99141...

...+ 241 18 clang 0x0000000000c012d6 clang::CodeGen::CodeGenFunction::EmitSimpleStmt(clang::Stmt const*) + 226 19 clang 0x0000000000c00de9 clang::CodeGen::CodeGenFunction::EmitStmt(clang::Stmt const*) + 75 20 clang 0x0000000000c19808 clang::CodeGen::CodeGenFunction::EmitFunctionBody(clang::CodeGen::FunctionArgList&) + 154 21 clang 0x0000000000c19d11 clang::CodeGen::CodeGenFunction::GenerateCode(clang::GlobalDecl, llvm::Function*, clang::CodeGen::CGFunctionInfo const&) + 971 22 clang 0x0000000000a9025f clang::CodeGen::CodeGenModule::EmitGlobalFun...

> If 3.9 shipped with these issues (assuming these are not false positive), it would be interesting to 1) know why the sanitizers didn’t catch it, and 2) add valgrind to the release qualification process (CC Hans). Yes, I'd be interested to see some corroboration. Note that the issue here is pretty specific: it only happens during optimized compile using Clang-3.9. This is all I did:

...lang 0x0000000000c012d6 clang::CodeGen::CodeGenFunction::EmitSimpleStmt(clang::Stmt const*) + 226 > 19 clang 0x0000000000c00de9 clang::CodeGen::CodeGenFunction::EmitStmt(clang::Stmt const*) + 75 > 20 clang 0x0000000000c19808 clang::CodeGen::CodeGenFunction::EmitFunctionBody(clang::CodeGen::FunctionArgList&) + 154 > 21 clang 0x0000000000c19d11 clang::CodeGen::CodeGenFunction::GenerateCode(clang::GlobalDecl, llvm::Function*, clang::CodeGen::CGFunctionInfo const&) + 971 > 22 clang 0x0000000000a9025f clang::CodeGen::CodeGenModule::Emi...

...ork, I need to treat my functions in the order they are in the original C file. I discovered that these functions are not treated in this order. My question is : Is there a way to force llvm to treat the functions in the order given in the original C file ? and how? I treat each function in the EmitFunctionBody funtion of the AsmPrinter class, and the function is passed through the MachineFunction passed trhough the runOnMachineFunction function. I didn't find where this last function is called. So I wish maybe to alter the way this function is called for each Function to call it in the "righ...

...g::CodeGen::CodeGenFunction::EmitSimpleStmt(clang::Stmt > > const*) + 226 > > 19 clang 0x0000000000c00de9 > > clang::CodeGen::CodeGenFunction::EmitStmt(clang::Stmt const*) + 75 > > 20 clang 0x0000000000c19808 > > clang::CodeGen::CodeGenFunction::EmitFunctionBody(clang::CodeGen::FunctionArgList&) > > + 154 > > 21 clang 0x0000000000c19d11 > > clang::CodeGen::CodeGenFunction::GenerateCode(clang::GlobalDecl, > > llvm::Function*, clang::CodeGen::CGFunctionInfo const&) + 971 > > 22 clang 0x0000000000a...

What program did you use to test the feature, and what was missing information? I'd like to file that as a bug so that we can fix this later. On Thu, Mar 16, 2017 at 2:34 PM, David Blaikie <dblaikie at gmail.com> wrote: > FWIW - selfhosting I did find that GDB wasn't able to find the source code > for some functions when using LLD's gdb_index, so I've switched back to

On Apr 20, 2012, at 6:35 PM, Roland Leißa <leissa at cs.uni-saarland.de> wrote: > ok, I now have a problem in the code generator. > Let's say I want to set a breakpoint somewhere in > clang/lib/CodeGen/CGExprScalar.cpp > > What do I have to do in order to trigger breakpoints, see backtraces and so on? You set a breakpoint and ask to see a backtrace? -eric

...et::NORTHERN_ISLANDS) { > EmitProgramInfoSI(MF); > } else { > EmitProgramInfoR600(MF); > } > + > + DisasmLines.clear(); > + HexLines.clear(); > + DisasmLineMaxLen = 0; > + > OutStreamer.SwitchSection(getObjFileLowering().getTextSection()); > EmitFunctionBody(); > + > + if (STM.dumpCode()) { > +#if !defined(NDEBUG) || defined(LLVM_ENABLE_DUMP) > + MF.dump(); > +#endif > + > + if (DisasmEnabled) { > + OutStreamer.SwitchSection(Context.getELFSection(".AMDGPU.disasm", > +...

ok, I now have a problem in the code generator. Let's say I want to set a breakpoint somewhere in clang/lib/CodeGen/CGExprScalar.cpp What do I have to do in order to trigger breakpoints, see backtraces and so on? -- Roland ----- Original Message ----- > From: "Eric Christopher" <echristo at apple.com> > To: "Roland Leißa" <leissa at cs.uni-saarland.de>

Hi, This patch adds R600/SI disassembly text to compiled object files, when a code dump is requested, to assist debugging in Mesa clients. Here's an example of the output in a Mesa client with a corresponding patch and RADEON_DUMP_SHADERS set: Shader Disassembly: S_WQM_B64 EXEC, EXEC ; BEFE0A7E S_MOV_B32 M0, SGPR6 ; BEFC0306

...x00007fb7119537d3 in > clang::CodeGen::CodeGenFunction::EmitCompoundStmtWithoutScope > (this=0x7fffd4fdc7e0, S=..., > GetLast=false, AggSlot=...) at > /u/geoff/llvmrepo/llvm-project/clang/lib/CodeGen/CGStmt.cpp:453 > #38 0x00007fb7119d69ec in > clang::CodeGen::CodeGenFunction::EmitFunctionBody > (this=0x7fffd4fdc7e0, Body=0x4a695e0) > at > /u/geoff/llvmrepo/llvm-project/clang/lib/CodeGen/CodeGenFunction.cpp:1147 > #39 0x00007fb7119d75bc in > clang::CodeGen::CodeGenFunction::GenerateCode (this=0x7fffd4fdc7e0, > GD=..., Fn=0x4699718, FnInfo=...) > at > /u/ge...

Greetings, Lang and other JITters, Last week I moved our Orc v2-based app from top-of-tree to the new 11.x branch, and it no longer handles C++ code containing OpenMP directives correctly. More specifically, if I JIT compile a function containing OpenMP parallel/for pragmas, using a release version of LLVM, the code compiles and seems to work, but if I try to write the module's bitcode to