similar to: [LLVMdev] "masm syntax" for X86 backend

2009/8/3 Anton Korobeynikov <anton at korobeynikov.info> > >> Anyway I wll report back when I have a proper overview of the area, > >> it would be good if you could also look into the problem so contact > >> me back if you are, also it maybe a good idea to share this with > >> Anton and Evan. > > > > I already spoke to anton. The MASM

>>  Anyway I wll report back when I have a proper overview of the area, >> it would be good if you could also look into the problem so contact >> me back if you are, also it maybe a good idea to share this with >> Anton and Evan. > > I already spoke to anton.  The MASM support is clearly broken, it > generates .s files with typos for the directives and has other

On Aug 3, 2009, at 12:04 PM, Aaron Gray wrote: > 2009/8/3 Anton Korobeynikov <anton at korobeynikov.info> > >> Anyway I wll report back when I have a proper overview of the > area, > >> it would be good if you could also look into the problem so contact > >> me back if you are, also it maybe a good idea to share this with > >> Anton and Evan.

On Monday 03 August 2009 14:04, Aaron Gray wrote: > 2009/8/3 Anton Korobeynikov <anton at korobeynikov.info> > > > >> Anyway I wll report back when I have a proper overview of the area, > > >> it would be good if you could also look into the problem so contact > > >> me back if you are, also it maybe a good idea to share this with > > >>

> The strainge thing is I believe VisualStudio can generate code through it > !:) That's only a belief :) vcpp-generated listings cannot be reassembled into objects via masm :( -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

On Tuesday 16 June 2009 09:48, Aaron Gray wrote: > Appently the GAS Intel backend has flaws and does not work correctly anyway > so the X86IntelAsm backend is designed only to target MASM anyway. gas Intel syntax is indeed broken in LLVM. I'd love to make it work but my work has not (yet) allocated time for that. Maybe I can hack LLVM on the weekends. :) The above discussion leads

On Jun 16, 2009, at 3:12 PM, David Greene wrote: > On Tuesday 16 June 2009 09:48, Aaron Gray wrote: > >> Appently the GAS Intel backend has flaws and does not work >> correctly anyway >> so the X86IntelAsm backend is designed only to target MASM anyway. > > gas Intel syntax is indeed broken in LLVM. I'd love to make it work > but > my work has not

> On Tuesday 16 June 2009 09:48, Aaron Gray wrote: > >> Appently the GAS Intel backend has flaws and does not work correctly >> anyway >> so the X86IntelAsm backend is designed only to target MASM anyway. > > gas Intel syntax is indeed broken in LLVM. I'd love to make it work but > my work has not (yet) allocated time for that. Maybe I can hack LLVM on >

>On Mon, Jun 15, 2009 at 5:49 PM, Gaster, >Benedict<Benedict.Gaster at amd.com> wrote: >> I would like to use the LLVM x86 code generator to emit Intel syntax that >> is >> compatible with Microsoft’s MASM 9.x. Taking the TOT LLVM, from last >> week, I >> have found a number of changes that are required to make this work, most >> of >> which

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) {

Hi, We have a significant regression since llvm 5.0.0 in the x86 assembler. The following snippets fail: 1) .intel_syntax 0: jmp 0b 2) .intel_syntax and edi, 0b010101 when running through `llvm-mc -arch x86-64`. This regression was introduced in r301390, which was driven by PR27884. I think https://llvm.org/PR36144 describes this very well, and I think we should get this fixed, since

On Tue, Jun 16, 2009 at 9:39 AM, Gaster, Benedict<Benedict.Gaster at amd.com> wrote: > Hi Eli, > > Yep I was being stupid. > > Please find attached a patch for initial changes to get MASM working. Patch looks fine except that it has tabs (LLVM uses only spaces for indentation). Also, can you generate the patch using "svn diff"? It's currently in some unusual

Hello, Benedict > 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: That's correct. MASM is too weak to represent even slightly non-trivial program. In your particular

I would like to use the LLVM x86 code generator to emit Intel syntax that is compatible with Microsoft's MASM 9.x. Taking the TOT LLVM, from last week, I have found a number of changes that are required to make this work, most of which are straight forward but a couple I wanted to check with the group to see what people thought was the best thing to do. In particular, I have made all necessary

On Mon, Jun 15, 2009 at 5:49 PM, Gaster, Benedict<Benedict.Gaster at amd.com> wrote: > I would like to use the LLVM x86 code generator to emit Intel syntax that is > compatible with Microsoft’s MASM 9.x. Taking the TOT LLVM, from last week, I > have found a number of changes that are required to make this work, most of > which are straight forward but a couple I wanted to check

On Aug 3, 2009, at 12:15 PM, David Greene wrote: > I would really hesistate in removing this. All of the Intel and AMD > manuals > use this syntax. Again, I'm not talking about the syntax, I'm talking about MASM *directive support*. -x86-asm-syntax=intel will still spit out "intel syntax" instructions. -Chris

> On Mon, 2005-07-11 at 19:24 +0100, Aaron Gray wrote: >> The NASM like the MASM does not have % symbols on the register names so >> will >> either inherit from the MASM printer or have its own TableGen class. > > Couldn't one conditionally output some macros for the assembler to > translate the reg names rather than having another .td file? or is '%'

>> I am not really sure whether to do a X86NASMPrinter or whether to bypass >> that for now and work on an X86COFFWriter which would be more useful to >> me ? > > I wouldn't suggest writing an X86NASMPrinter: just change the current > Intel printer to do what you want. Noone is currently using the intel > printer, so you can do what you wish to it. Once I

Hi LLVM'ers, has anyone read the license details for MASM32 and understood how these fit in with Open Source projects, especially GPL? - As far as I can see - no one is allowed to license projects under GPL or at worst other OS licenses nor the deritives of the project, if you're using MASM32. Are the MASM backend compatible with the MS version of MASM or other not so license

Here's the new MASM backend. It has the following files :- lib/Target/X86/X86AsmPrinter.h lib/Target/X86/X86AsmPrinter.cpp lib/Target/X86/X86MASMPrinter.h lib/Target/X86/X86MASMPrinter.cpp lib/Target/X86/X86.td lib/Target/X86/X86InstrInfo.td lib/Target/X86/makefile Makefile.rules win32/x86/x86.vcproj