search for: masm

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 me to believe there are fundamental conflicts between MASM and gas syntax. Is NASM any bette...

>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 with the group >> to >> see what people thought was the best thing to...

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 (yet) allocated time for that. Maybe I can hack > LLVM on > the weekends. :) > > The above discussion leads me to believe there are fundamental > conflicts...

> 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 ...

...FWriter 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 have finished rewriting the MASM printer then a NASM one should take no time at all, he says :) 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. >> Also looking at your ELF code I do not know how to fit it in exactly with &g...

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

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/make...

> 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. :) I think writing an assembler using LLVM Table gen and data, and using the DOCE (Direct Object Code Em...

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...

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 '%' not a valid part o...

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 format which "patch" doesn't recognize. > There is still one problem that I am looking into...

...ll 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 > > problems. Anton thinks it should be removed. > The reason is pretty simple: masm is too weak to support anything > non-trivial and unfortunatley there is no simple way to fix the...

...ug 3, 2009, at 11:23 AM, Aaron Gray wrote: > Hi Chris, > > It would be good to get to try to get it as functional as possible > at some point, before abandoning it..maye once I have one the COFF > backend. I'm not proposing to remove COFF support from the asmprinter, just masm support. Using gas will continue to work fine. > 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 alr...

Even the latest version of MASM does not support the CMOVcc instructions (unless they are named something different my Microsoft ?). Using the CMOVcc instruction rules the X86 out for compilation to pre Pentium Pro CPU's. Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists....

On Mon, Jun 15, 2009 at 11:21 PM, Gaster, Benedict<Benedict.Gaster at amd.com> wrote: > I can get this two work with additional changes to X86InstrInfocpp but > the problem I have with this approach is that it introduces a lot of > duplication, when all I really want to do is parameterize the final > field in the string "shl{b}\t{%cl, $dst|$dst, %CL}". I was wondering

Hi all, I'm working on a project that uses clang-cl & lld-link to build for Windows, along with some tools out of the Windows SDK... but we're currently pre-building some pieces of MASM assembly code using Microsoft's ml.exe & ml64.exe. Unfortunately, it's not all inline assembly, which clang can already handle, and Microsoft's file-level directives are a bit unusual. I plan to work on getting llvm-mc to compile (relatively simple) MASM files when targeting a Wind...

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 case - LLVM IR can set up any alignment it want...

...th Emacs and the svn diff is attached. Regards, Ben -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Eli Friedman Sent: Tuesday, June 16, 2009 11:19 AM To: LLVM Developers Mailing List Subject: Re: [LLVMdev] x86 Intel Syntax and MASM 9.x 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 indenta...

On Sat, 9 Jul 2005, Aaron Gray wrote: > Even the latest version of MASM does not support the CMOVcc instructions > (unless they are named something different my Microsoft ?). Using the > CMOVcc instruction rules the X86 out for compilation to pre Pentium Pro > CPU's. You probably have to emit a directive that enables ppro and higher opcodes. Maybe so...

On Mon, 11 Jul 2005, Aaron Gray wrote: >> 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...