search for: x86attasmprint

This looks like pr4572. Evan On Jul 27, 2009, at 3:25 AM, Aaron Gray wrote: > I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 > right near the end of compiling llvm-gcc in valarray-inst.cc. > > assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow > scaling by ESP" > > Does this build on Linux ? > > My remote Linux box ha...

I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 right near the end of compiling llvm-gcc in valarray-inst.cc. assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow scaling by ESP" Does this build on Linux ? My remote Linux box has died and not a ble to reset it for a da...

I am now getting the following link errors on all executables: x86.lib(X86AsmPrinter.obj) : error LNK2001: unresolved external symbol "public: virtual bool __thiscall llvm::x86::X86ATTAsmPrinter::runOnMachineFunction(class llvm::MachineFunction &)" (?runOnMachineFunction at X86ATTAsmPrinter@x86 at llvm@@UAE_NAAVMachineFunction at 3@@Z) x86.lib(X86AsmPrinter.obj) : error LNK2001: unresolved external symbol "public: virtual bool __thiscall llvm::x86::X86IntelAsmPrinter::r...

...ibdecnumber -I../libdecnumber -I/home/regehr/llvm/include -I/home/regehr/llvm/include -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-toplevel-reorder -fno-omit-frame-pointer \ -c ../../gcc/crtstuff.c -DCRT_BEGIN \ -o crtbegin.o cc1: X86ATTAsmPrinter.cpp:543: void llvm::X86ATTAsmPrinter::printMemReference(const llvm::MachineInstr*, unsigned int, const char*): Assertion `isMem(MI, Op) && "Invalid memory reference!"' failed. ../../gcc/crtstuff.c:378: internal compiler error: Aborted Please submit a full bug report, with...

...(phew!, and thanks for all the help!), but I get linker errors now: llvm[3]: Linking Release Object Library LLVMX86.o llvm[3]: Compiling DelaySlotFiller.cpp for Release build /usr/bin/ld: Relocatable linking with relocations from format elf64-x86-64 (/home/jo/Delta/llvm-2.2/lib/Target/X86/Release/X86ATTAsmPrinter.o) to format elf32-i386 (/home/jo/Delta/llvm-2.2/Release/lib/LLVMX86.o) is not supported make[3]: *** [/home/jo/Delta/llvm-2.2/Release/lib/LLVMX86.o] Fehler 1 Seems like was told to link lib/Target/X86/Release/X86ATTAsmPrinter.o (which is 64-bit) and Release/lib/LLVMX86.o (which is 32-bit). The...

Chris, Okay, I have done as you have requested. The only thing I did not like was a clsh between the enum X86 and the new namespace X86, which I had to rename as x86 :( Anyway, I suppose the lower case 'x' in 'x86' fits in with the lowercase 'llvm' namespace. Build tested on MS VC2003 and Linux. Aaron -------------- next part -------------- A non-text attachment was

...llvm\lib\Target\X86\X86AsmPrinter.cpp(364) : error C2264: '`anonymous-namespace'::X86IntelAsmPrinter::printInstruction' : error in function definition or declaration; function not called tablegen_includes\X86GenATTAsmWriter.inc(15) : error C2888: 'bool `anonymous-namespace'::X86ATTAsmPrinter::printInstruction(const llvm::MachineInstr *)' : symbol cannot be defined within namespace 'llvm' tablegen_includes\X86GenATTAsmWriter.inc(469) : fatal error C1204: compiler limit : internal structure overflow scons: *** [build_vc71\lib\Target\X86\X86AsmPrinter.obj] Error 2 scons:...

Another warning: r:\sdks\llvm\trunk\lib\target\x86\asmprinter\X86ATTAsmPrinter.h(29) : warning C4099: 'llvm::MachineJumpTableInfo' : type name first seen using 'class' now seen using 'struct' R:\SDKs\llvm\trunk\include\llvm/CodeGen/MachineFunction.h(34) : see declaration of 'llvm::MachineJumpTableInfo' The problem appears to be in f...

On Friday 10 July 2009 00:19, Chris Lattner wrote: > asmprinter::printInstruction will lower a MachineInstr to an MCInst, > then call the MCInst asmprinter to do the hard formatting work. You > can see a horrible simple skeleton of this idea in > X86ATTAsmPrinter::printMachineInstruction. Yep, that's where I hit the problem. I'm patching the sources for the comment emitter and of course MCInst doesn't have the right interfaces yet. > > I'm porting some > > patches we have here that affect MachineInstrs and am wondering >...

...anguage.h(32) : warning C4099: 'llvm::SourceLanguage' : type name first seen using 'class' now seen using 'struct' 14> C:\llvm\include\llvm/Debugger/ProgramInfo.h(33) : see declaration of 'llvm::SourceLanguage' 16>c:\dj\llvm\lib\target\x86\asmprinter\X86ATTAsmPrinter.h(29) : warning C4099: 'llvm::MachineJumpTableInfo' : type name first seen using 'class' now seen using 'struct' 16> C:\llvm\include\llvm/CodeGen/MachineFunction.h(34) : see declaration of 'llvm::MachineJumpTableInfo' 16>c:\dj\llvm\lib\target\x86\a...

...oring, instruction asmprinting (for example) will no longer work directly on MachineInstr. Instead, asmprinter::printInstruction will lower a MachineInstr to an MCInst, then call the MCInst asmprinter to do the hard formatting work. You can see a horrible simple skeleton of this idea in X86ATTAsmPrinter::printMachineInstruction. There is a ton of refactoring and cleanup left to do, but a great benefit of this is that it really helps clean up the targets and make them do the right things in the right places. > I'm porting some > patches we have here that affect MachineInstrs and a...

...dio (or at least forgot to include x86.vcproj with the other files). Jeff Cohen wrote: > I am now getting the following link errors on all executables: > > x86.lib(X86AsmPrinter.obj) : error LNK2001: unresolved external symbol > "public: virtual bool __thiscall > llvm::x86::X86ATTAsmPrinter::runOnMachineFunction(class > llvm::MachineFunction &)" > (?runOnMachineFunction at X86ATTAsmPrinter@x86 at llvm@@UAE_NAAVMachineFunction at 3@@Z) > > x86.lib(X86AsmPrinter.obj) : error LNK2001: unresolved external symbol > "public: virtual bool __thiscall > l...

Can someone explain what MCInst is vs. MachineIntr? I'm porting some patches we have here that affect MachineInstrs and am wondering whether I need to make similar changes in MCInst. Why do we have two machine instruction representations? -Dave

...ake :)) I do not know whether it is a good idea to split the X86AsmPrinter.cpp class up into a '.h' file as well as a '.cpp' file thus allowing the NASMPrinter to be in a separate '.cpp' file or not. Also it would be possible to split X86AsmPrinter, X86IntelAsmPrinter, and X86ATTAsmPrinter up into different '.cpp' files and either a common or separate headers. Should I do this ? There are another couple of other issues I would like advice on :- One is testing how to go about testing the NASM backend and integrating the testing with the existing test framework. The other...

...his in the AsmPrinter, with operand modifiers. For example, on x86 there are instructions with ${dst:call} in their asm string. The "call" part is interpreted as an operand modifier. The assembly printer looks for the "call" modifier on MachineOperand::MO_Immediate operands (in X86ATTAsmPrinter::printOperand), which lets it perform custom printing for that type of operand. You could use a modifier which tells the AsmPrinter to print an immediate as the appropriate letter. Dan On May 5, 2009, at 10:23 PM, Manjunath Kudlur wrote: > Hello, > > I am trying to create a machine i...

...\X86AsmPrinter.cpp(364) : error C2264: > '`anonymous-namespace'::X86IntelAsmPrinter::printInstruction' : error in > function definition or declaration; function not called > tablegen_includes\X86GenATTAsmWriter.inc(15) : error C2888: 'bool > `anonymous-namespace'::X86ATTAsmPrinter::printInstruction(const > llvm::MachineInstr *)' : symbol cannot be defined within namespace 'llvm' > tablegen_includes\X86GenATTAsmWriter.inc(469) : fatal error C1204: > compiler limit : internal structure overflow > > scons: *** [build_vc71\lib\Target\X86\X86AsmPri...

Hello, I am trying to create a machine instruction for "extractelement". I want to translate r <- extractelement v, 0 to mov r, v.x I was looking at the dag I can use and I found vector_extract. The inputs for this SDnode are a register and a iPtr constant. With that, I need to create 4 separate def's to extract element 0, 1, 2, and 3 and translate to v.x, v.y, v.z, and v.w. I

...perand modifiers. > > For example, on x86 there are instructions with ${dst:call} in > their asm string. The "call" part is interpreted as an operand > modifier. The assembly printer looks for the "call" modifier > on MachineOperand::MO_Immediate operands > (in X86ATTAsmPrinter::printOperand), which lets it perform custom > printing for that type of operand. You could use a modifier which > tells the AsmPrinter to print an immediate as the appropriate > letter. > > Dan > > > On May 5, 2009, at 10:23 PM, Manjunath Kudlur wrote: > >> Hello...

...perand modifiers. > > For example, on x86 there are instructions with ${dst:call} in > their asm string. The "call" part is interpreted as an operand > modifier. The assembly printer looks for the "call" modifier > on MachineOperand::MO_Immediate operands > (in X86ATTAsmPrinter::printOperand), which lets it perform custom > printing for that type of operand. You could use a modifier which > tells the AsmPrinter to print an immediate as the appropriate > letter. > > Dan > > > On May 5, 2009, at 10:23 PM, Manjunath Kudlur wrote: > >> Hello...

...just scan for \n and \r in the memory range. +std::string stringFromMCInst_x86(const MCInst& insn, + const Target* target, + std::string& triple) { Please mark this static so that you can shrink the anon namespace. + X86ATTAsmPrinter* asmPrinter = + dynamic_cast<X86ATTAsmPrinter*>(functionPass); Please don't use dynamic_cast: we're trying to eliminate RTTI a C cast should be fine. +int HexDisassembler::disassemble(const Target* target, + LineReader& reader) { ... + +...