search for: asmprinter

Seems like something infinite-recursion like to me: $ clang --version clang version 6.0.0 (trunk 317833) Target: powerpc64le-unknown-linux-gnu $ clang -c test.ll warning: overriding the module target triple with powerpc64le-unknown-linux-gnu [-Woverride-module] ... #255 0x0000000012b07a78 llvm::DwarfUnit::getOrCreateTypeDIE(llvm::MDNode const*) ... So I'd say it reproduces. On Wed, Nov 15,

Hi, While trying to debug a linking problem related to AsmPrinter, I found following lines in {srcdir}/configure file. if test -f ${srcdir}/lib/Target/${target_to_build}/*AsmPrinter.cpp ; then LLVM_ENUM_ASM_PRINTERS="LLVM_ASM_PRINTER($target_to_build) $LLVM_ENUM_ASM_PRINTERS"; It looks like the AsmPrinters are enumerated only if *AsmPrinter.cpp...

...assertion failures in llvm::DbgVariable::addMMIEntry: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/1816/steps/check-msan%20in%20gcc%20build/logs/stdio I did not find the offender yet. Any ideas? clang-5.0: /mnt/b/sanitizer-buildbot1/sanitizer-x86_64-linux/build/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.h:131: void llvm::DbgVariable::addMMIEntry(const llvm::DbgVariable&): Assertion `V.Var == Var && "conflicting variable"' failed. clang-5.0: /mnt/b/sanitizer-buildbot1/sanitizer-x86_64-linux/build/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.h:131: void llvm::DbgVariab...

Hi everyone, I am in the process of adding some new code for th ARM/MC ELF emission, but noticed a curious linkage between th AsmPrinter and the MC. It looks like the MC code (on X86 at least) calls out to the (misnamed?) AsmPrinter to dump out ELF bits (in X86AsmPrinter.cpp) in the same routine, using conditional branching.... As JimG and I are working both on ARM emission stuff, I want to minimize chances of us stomping on each...

I'm looking at extending AsmPrinter to pretty-print comments after instructions (I'm adding the necessary fields to MachineInstr to do this). I'm trying to grok AsmWriterEmitter and having a tough go of it. I look at X86GenAsmWriter1.inc (the Intel syntax writer) and understand that there's a case block for printing o...

I have been looking over AsmPrinter::EmitLinkage (around line 195 of lib\CodeGen\AsmPrinter\AsmPrinter.cpp) and it seems that its implementation will vary quite a bit depending on what object file format is in use (MachO, ELF, or COFF). Would it make sense to delegate the implementation to a specialized object from current the obje...

...e it using our built in DWARF parser and validate that the API calls we do when consuming the DWARF match what we expect. The original stand along DWARF generator class is in unittests/DebugInfo/DWARF/DWARFGenerator2.{h,cpp} in the patch attached. The original review suggested that I try to use the AsmPrinter and many of its associated classes to generate the DWARF. I attempted to do so and the AsmPrinter version is in lib/CodeGen/DwarfGenerator.{h,cpp} in the patch attached. This AsmPrinter based code steals code from the DwarfLinker.cpp. > > > > I am having trouble getting things to wor...

On May 10, 2010, at 6:46 PM, Nathan Jeffords wrote: > I have been looking over AsmPrinter::EmitLinkage (around line 195 of lib\CodeGen\AsmPrinter\AsmPrinter.cpp) and it seems that its implementation will vary quite a bit depending on what object file format is in use (MachO, ELF, or COFF). > Would it make sense to delegate the implementation to a specialized object from current the...

...e it using our built in DWARF parser and validate that the API calls we do when consuming the DWARF match what we expect. The original stand along DWARF generator class is in unittests/DebugInfo/DWARF/DWARFGenerator2.{h,cpp} in the patch attached. The original review suggested that I try to use the AsmPrinter and many of its associated classes to generate the DWARF. I attempted to do so and the AsmPrinter version is in lib/CodeGen/DwarfGenerator.{h,cpp} in the patch attached. This AsmPrinter based code steals code from the DwarfLinker.cpp. -------------- next part -------------- A non-text attachment...

...MMIEntry: >> http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/ >> builds/1816/steps/check-msan%20in%20gcc%20build/logs/stdio >> I did not find the offender yet. Any ideas? >> >> clang-5.0: /mnt/b/sanitizer-buildbot1/sanitizer-x86_64-linux/build/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.h:131: void llvm::DbgVariable::addMMIEntry(const llvm::DbgVariable&): Assertion `V.Var == Var && "conflicting variable"' failed. >> clang-5.0: /mnt/b/sanitizer-buildbot1/sanitizer-x86_64-linux/build/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.h:131: void llvm::...

On Fri, 10 Aug 2007, David Greene wrote: > I'm looking at extending AsmPrinter to pretty-print comments after > instructions (I'm adding the necessary fields to MachineInstr to do this). ok > I also have a few questions on the general design of AsmPrinter. Why is > runOnMachineFunction implemented for each target AsmPrinter? I would Historical reasons that a...

Hi XCore and PIC16 maintainers, I'd appreciate it if you guys could move your AsmPrinter implementation to be in a subdirectory like the rest of the other targets (e.g. make it live in lib/Target/PIC16/AsmPrinter). Anton is planning to move MSP430 to use the same approach. Having all the targets use the same design simplifies the build system and keeps the target architectu...

...and validate that the >> API calls we do when consuming the DWARF match what we expect. The >> original stand along DWARF generator class is in >> unittests/DebugInfo/DWARF/DWARFGenerator2.{h,cpp} in the patch attached. >> The original review suggested that I try to use the AsmPrinter and many of >> its associated classes to generate the DWARF. I attempted to do so and the >> AsmPrinter version is in lib/CodeGen/DwarfGenerator.{h,cpp} in the patch >> attached. This AsmPrinter based code steals code from the DwarfLinker.cpp. >>> >>> >>&...

The Microsoft CRT's implementation of isprint() has an internal assert that the unsigned value passed in is in [0,256) but unprintable chars passed in are sign extended to values that falsely trigger this assert. --- c:\usr\src\llvm-svn\lib\CodeGen\AsmPrinter\AsmPrinter.cpp Tue Jan 20 10:30:42 2009 +++ c:\usr\src\llvm-integrate\lib\CodeGen\AsmPrinter\AsmPrinter.cpp Thu Jan 22 15:19:47 2009 @@ -681,7 +681,7 @@ O << "\\\""; } else if (C == '\\') { O << "\\\\"; - } else if (isprint(C)) { + } els...

...he > >> API calls we do when consuming the DWARF match what we expect. The > >> original stand along DWARF generator class is in > >> unittests/DebugInfo/DWARF/DWARFGenerator2.{h,cpp} in the patch attached. > >> The original review suggested that I try to use the AsmPrinter and many > of > >> its associated classes to generate the DWARF. I attempted to do so and > the > >> AsmPrinter version is in lib/CodeGen/DwarfGenerator.{h,cpp} in the patch > >> attached. This AsmPrinter based code steals code from the > DwarfLinker.cpp. > &g...

...ached; dot file follows. digraph G { ipo [shape=box,style=filled,color=olivedrab1]; ipa [shape=box,style=filled,color=olivedrab1]; X86Info [shape=box,style=filled,color=olivedrab1]; X86Disassembler [shape=box,style=filled,color=olivedrab1]; X86CodeGen [shape=box,style=filled,color=olivedrab1]; X86AsmPrinter [shape=box,style=filled,color=olivedrab1]; X86AsmParser [shape=box,style=filled,color=olivedrab1]; TransformUtils [shape=box,style=filled,color=olivedrab1]; Target [shape=box,style=filled,color=olivedrab1]; System [shape=box,style=filled,color=olivedrab1]; Support [shape=box,style=filled,color=oliv...

> Chris Lattner wrote: > >> Hi XCore and PIC16 maintainers, >> >> I'd appreciate it if you guys could move your AsmPrinter >> implementation to be in a subdirectory like the rest of the other >> targets (e.g. make it live in lib/Target/PIC16/AsmPrinter). >> I've moved the XCore AsmPrinter in r79094: http://llvm.org/viewvc/llvm-project?rev=79094&view=rev

On Mon, May 10, 2010 at 9:43 PM, Chris Lattner <clattner at apple.com> wrote: > > On May 10, 2010, at 6:46 PM, Nathan Jeffords wrote: > > > I have been looking over AsmPrinter::EmitLinkage (around line 195 of > lib\CodeGen\AsmPrinter\AsmPrinter.cpp) and it seems that its implementation > will vary quite a bit depending on what object file format is in use (MachO, > ELF, or COFF). > > Would it make sense to delegate the implementation to a specialized >...

Hello everyone, In the file *lib/CodeGen/AsmPrinter/AsmPrinter.cpp*, I would like to obtain an MCInst corresponding to its MachineInstr. Can anyone tell me a way to do that? If that is not possible, then, I would like to know if a given MachineInstr is an *lea *instruction and I would like to know if the symbol involved with this lea instruction is...

...:X86FrameLowering::getFrameIndexReference(class llvm::MachineFunction const &,int,unsigned int &)const c:\p\llvm\llvm\lib\target\x86\x86framelowering.cpp:1672:0 ; #1 0x00f99010 llvm::WinException::getFrameIndexOffset(int,struct 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\cod...