search for: x86intelasmprint

A possible minor bug in lib/Target/X86/X86IntelAsmPrinter.cpp X86IntelAsmPrinter::doInitialization is calling AsmPrinter::doInitialization() not X86SharedAsmPrinter::doInitialization() Supprised I did not spot it earlier. Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev...

...::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::runOnMachineFunction(class llvm::MachineFunction &)" (?runOnMachineFunction at X86IntelAsmPrinter@x86 at llvm@@UAE_NAAVMachineFunction at 3@@Z) x86.lib(X86AsmPrinter.obj) : error LNK2001: unresolved external symbol "public: virtual bool __thiscall llvm::x86::X86IntelAsmPrinter:...

Hi again, I have put together a "blank skeleton" for a X86NASMPrinter class, with effectively the same behaviour as the X86IntelAsmPrinter class. I had to do this within the X86AsmPrinter.cpp file rather than as a separate source file as the dependancies were so. Please do not commit this yet, I have included it not for confidence sake :)) I do not know whether it is a good idea to split the X86AsmPrinter.cpp class up into a '....

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

Hello, I would like to know how to go about printing the x86 assembly output for a compiled function (I'm using the JIT). I saw there is a X86IntelAsmPrinter on doxygen. However, it takes several arguments I don't know how to fill in. Is there a helper function to create such a pass? Once I have the pass created, do I just add it to a FunctionPassManager? Thank you for your time, - Maxime -- View this message in context: http://www.nabble.com/P...

...r your asmprinters. >> >> I dont think printOp is virtual and therefore cannot be overriden ? > > Why does it need to be virtual? No 'intel' printers want % signs. The GAS intel code generator generates percents, look at the X86InstrInfo.td file it is full of them. The X86IntelAsmPrinter is not overridable and inheritable for this job. The X86MASMPrinter overrides too much for the Intel one to be useful. Aaron

...OAT_H /DHAVE__ISNAN_IN_FLOAT_H /ISTLport-4.6.2\stlport /Illvm\inc lude /Itablegen_includes /c llvm\lib\Target\X86\X86AsmPrinter.cpp /Fobuild_vc71\lib\Target\X86\X86AsmPrinter.obj X86AsmPrinter.cpp tablegen_includes\X86GenIntelAsmWriter.inc(15) : error C2888: 'bool `anonymous-namespace'::X86IntelAsmPrinter::printInstruction(const llvm::MachineInstr *)' : symbol cannot be defined within namespace 'llvm' llvm\lib\Target\X86\X86AsmPrinter.cpp(364) : error C2264: '`anonymous-namespace'::X86IntelAsmPrinter::printInstruction' : error in function definition or declaration; funct...

Dear Maxime, Nyx wrote: > Hello, > > I would like to know how to go about printing the x86 assembly output for a > compiled function (I'm using the JIT). I saw there is a X86IntelAsmPrinter > on doxygen. However, it takes several arguments I don't know how to fill in. > Is there a helper function to create such a pass? Once I have the pass > created, do I just add it to a FunctionPassManager? > > X86IntelAsmPrinter is used when compiling to an assembly file. I...

...rr : I<0xEC, RawFrm, (ops), "in{b} {%dx, %al|%AL, %DX}">, Imp<[DX], [AL]>; to: def IN8rr : I<0xEC, RawFrm, (ops), "in{b} {%dx, %al|AL, DX}">, Imp<[DX], [AL]>; For register allocatable values, changing printOp in the X86IntelAsmPrinter should do the job. > The X86IntelAsmPrinter is not overridable and inheritable for this job. The > X86MASMPrinter overrides too much for the Intel one to be useful. Again, there is *nothing* currently using the 'intel' asm printer. Feel free to change it however you find conven...

..."in{b} {%dx, %al|%AL, %DX}">, Imp<[DX], [AL]>; > > to: > > def IN8rr : I<0xEC, RawFrm, (ops), > "in{b} {%dx, %al|AL, DX}">, Imp<[DX], [AL]>; > > For register allocatable values, changing printOp in the > X86IntelAsmPrinter should do the job. Yes GNU AS works either with or without % symbols for its register names. So presumably we remove the percents from the intel generator and then have the X86MASMPrinter inherit from the X86IntelAsmPrinter as was originally intended. > Also, when you do things like this,...

...achineFunction(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::runOnMachineFunction(class > llvm::MachineFunction &)" > (?runOnMachineFunction at X86IntelAsmPrinter@x86 at llvm@@UAE_NAAVMachineFunction at 3@@Z) > > x86.lib(X86AsmPrinter.obj) : error LNK2001: unresolved external symbol > "public: virtual bool __thiscall >...

...> /ISTLport-4.6.2\stlport /Illvm\inc > lude /Itablegen_includes /c llvm\lib\Target\X86\X86AsmPrinter.cpp > /Fobuild_vc71\lib\Target\X86\X86AsmPrinter.obj X86AsmPrinter.cpp > > tablegen_includes\X86GenIntelAsmWriter.inc(15) : error C2888: 'bool > `anonymous-namespace'::X86IntelAsmPrinter::printInstruction(const > llvm::MachineInstr *)' : symbol cannot be defined within namespace 'llvm' > llvm\lib\Target\X86\X86AsmPrinter.cpp(364) : error C2264: > '`anonymous-namespace'::X86IntelAsmPrinter::printInstruction' : error in > function definition o...

...default being 16, but LLVM is sometimes generating 32 > alignment, for example, consider the following code: That's correct. MASM is too weak to represent even slightly non-trivial program. In your particular case - LLVM IR can set up any alignment it want. Also note the FIXME's in the X86IntelAsmPrinter.cpp wrt the alignment. You might try to round up the alignment to the highest allowed value, but this might be an overkill... -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

...sts. Aaron ----- Original Message ----- From: Aaron Gray To: LLVM Developers Mailing List Sent: Tuesday, May 10, 2005 5:26 PM Subject: NASM Backend Hi again, I have put together a "blank skeleton" for a X86NASMPrinter class, with effectively the same behaviour as the X86IntelAsmPrinter class. I had to do this within the X86AsmPrinter.cpp file rather than as a separate source file as the dependancies were so. Please do not commit this yet, I have included it not for confidence sake :)) I do not know whether it is a good idea to split the X86AsmPrinter.cpp class up into a '...

On Tue, 10 May 2005, Aaron Gray wrote: > I have put together a "blank skeleton" for a X86NASMPrinter class, with > effectively the same behaviour as the X86IntelAsmPrinter class. I had to > do this within the X86AsmPrinter.cpp file rather than as a separate > source file as the dependancies were so. Please do not commit this yet, > I have included it not for confidence sake :)) Ok. > I do not know whether it is a good idea to split the X86AsmPrinte...

On Wednesday 17 June 2009 00:11, Evan Cheng wrote: > Asm printer. Yes, but where? I can't find it. What do I need to search for? -Dave

> On Wednesday 17 June 2009 00:11, Evan Cheng wrote: >> Asm printer. > > Yes, but where? I can't find it. What do I need to > search for? ViewVC is helpful :- http://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Target/X86/AsmPrinter/ Look at the X86IntelAsmPrinter.cpp file for code outputting the align, if its not there it maybe in the X86AsmPrinter.cpp file, meaning you may have to override the functionality in the X86AsmPrinter.h and cpp file. Aaron

...%dx, %al|%AL, %DX}">, Imp<[DX], [AL]>; >> >> to: >> >> def IN8rr : I<0xEC, RawFrm, (ops), >> "in{b} {%dx, %al|AL, DX}">, Imp<[DX], [AL]>; >> >> For register allocatable values, changing printOp in the X86IntelAsmPrinter >> should do the job. > > Yes GNU AS works either with or without % symbols for its register names. So > presumably we remove the percents from the intel generator and then have the > X86MASMPrinter inherit from the X86IntelAsmPrinter as was originally > intended. Please...

Hi Eli, Yep I was being stupid. Please find attached a patch for initial changes to get MASM working. There is still one problem that I am looking into around changing alignments within SEGMENTS. The problem is that MASM allows 2,4,16,256 alignments, default being 16, but LLVM is sometimes generating 32 alignment, for example, consider the following code: float bar(float fy, float fx) {

...an tell it seems that the LLVM x86 backend targets GNU >assembler with DWARF for debug and there is not a way, currently, to >output for MS assembler with COFF debug info. Is this correct or am I >just looking at the wrong part? Multiple issues here, actually. First of all, there is "X86IntelAsmPrinter", which outputs MASM-compatible assembler. You can select assembler flavour via command line, for example. However, MASM is really weak to support all necessary features for compilation of something huge and complex (MS tools do not emit assembler directly, their assembler listings are pu...