search for: emitint8

DwarfDebug::emitDebugInfo() always appends four zero bytes to the tail of the debug info section: emitDIE(Die); // FIXME - extra padding for gdb bug. Asm->OutStreamer.AddComment("4 extra padding bytes for GDB"); Asm->EmitInt8(0); Asm->EmitInt8(0); Asm->EmitInt8(0); Asm->EmitInt8(0); Asm->OutStreamer.EmitLabel(Asm->GetTempSymbol("info_end", TheCU->getID())); Does anybody know what the bug is in GDB that this works around? The workaround was added as part of r103439[1], which a...

...hod > + /// returns true (the callee is required to try again), > otherwise it returns > + /// false. > + /// > + virtual bool finishFunction(MachineFunction &F, unsigned char* > FnStart, > + unsigned char* FnEnd) = 0; > + > + /// EmitInt8 - This callback is invoked when a byte needs to be > written to the > + /// output stream. > + /// > + void EmitInt8(unsigned char B, bool print=true) { > +// if (print) printf(".byte 0x%x\n", B); > + if (CurBufferPtr != BufferEnd) > + *CurBufferPtr++...

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

...e callee is required to try again), >> otherwise it returns >> + /// false. >> + /// >> + virtual bool finishFunction(MachineFunction &F, unsigned char* >> FnStart, >> + unsigned char* FnEnd) = 0; >> + >> + /// EmitInt8 - This callback is invoked when a byte needs to be >> written to the >> + /// output stream. >> + /// >> + void EmitInt8(unsigned char B, bool print=true) { >> +// if (print) printf(".byte 0x%x\n", B); >> + if (CurBufferPtr != BufferEnd) >...

..., Ken Dyck wrote: > DwarfDebug::emitDebugInfo() always appends four zero bytes to the tail > of the debug info section: > > emitDIE(Die); > // FIXME - extra padding for gdb bug. > Asm->OutStreamer.AddComment("4 extra padding bytes for GDB"); > Asm->EmitInt8(0); > Asm->EmitInt8(0); > Asm->EmitInt8(0); > Asm->EmitInt8(0); > Asm->OutStreamer.EmitLabel(Asm->GetTempSymbol("info_end", TheCU->getID())); > > Does anybody know what the bug is in GDB that this works around? The > workaround was added...

Hi all, The AsmPrinter class supports functions like EmitInt8, EmitInt16, and EmitInt32 for writing a 1/2/4 byte directive to the assembly. Each of these calls the MCStreamer::EmitIntValue method with the corresponding size. For some reason, there is no EmitInt64, and I was wondering if there was a fundamental reason why? The EmitIntValue function appears to...

...seems very reasonable.) --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of James Henderson via llvm-dev Sent: Friday, March 09, 2018 7:44 AM To: llvm-dev Subject: [llvm-dev] Why is there no EmitInt64 in AsmPrinter? Hi all, The AsmPrinter class supports functions like EmitInt8, EmitInt16, and EmitInt32 for writing a 1/2/4 byte directive to the assembly. Each of these calls the MCStreamer::EmitIntValue method with the corresponding size. For some reason, there is no EmitInt64, and I was wondering if there was a fundamental reason why? The EmitIntValue function appears to...

On Mon, Aug 10, 2020 at 5:15 AM Alexey Lapshin <avl.lapshin at gmail.com> wrote: > > Hi Jonas, > > Thank you for the comments, please find my answers below... > > On 06.08.2020 20:39, Jonas Devlieghere wrote: > > Hi Alexey, > > I should've looked at this earlier. I went through the thread again and I've > made some comments, mostly from the dsymutil