"masm syntax" for X86 backend

Is anyone using the -x86-asm-syntax=intel flag to llc or otherwise using the MASM .s file printing stuff in the X86 backend? My understanding is that masm is really not very useful, and that the code doesn't really work.

Going forward, we'd like to be able to just emit a PECOFF file direction, and we will continue to support mingw, so windows plaform support really won't use this.

Is this true? If so, I'd like to consider removing support for masm. We'd still be able to support mingw/gas on windows, and we'd still support gas-style intel assembly. I'm only talking about masm directives etc.

-Chris

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

-Chris

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

2009/8/3 Anton Korobeynikov <anton@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 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 stuff.

The strainge thing is I believe VisualStudio can generate code through it !:slight_smile:

Anyway I agree cut it for now as it is non functonal.

Aaron

2009/8/3 Anton Korobeynikov <anton@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 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 stuff.

The strainge thing is I believe VisualStudio can generate code through it !:slight_smile:

No, it doesn’t, it writes .o files directly iiuc.

-Chris

I would really hesistate in removing this. All of the Intel and AMD manuals
use this syntax.

Certainly the printer needs some work and I've actually got it on my TODO list
to look at it. I won't be able to get to it for a while, though.

It's not a simple matter of deleting files, as all of the X86 .td files will
need to be changed as well.

Is there some excessive cost we're trying to get rid of? What's wrong with
keeping it there?

                                      -Dave

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

Ah, ok. I'm fine with this then.

                                -Dave

The strainge thing is I believe VisualStudio can generate code through it
!:slight_smile:

That's only a belief :slight_smile: vcpp-generated listings cannot be reassembled
into objects via masm :frowning:

2009/8/3 Chris Lattner <clattner@apple.com>

2009/8/3 Anton Korobeynikov <anton@korobeynikov.info>

The strainge thing is I believe VisualStudio can generate code through it
!:slight_smile:

That’s only a belief :slight_smile: vcpp-generated listings cannot be reassembled
into objects via masm :frowning:

Ah !

Thats nice of Microsoft, a nice listing facility !

Aaron