> Ok, less talk and more action. I just implemented proper Microsoft > ML/MASM support. It probably has a few rough edges, so if anyone wants to > try it out please do and let me know if you encounter any problems. > > Note that you cannot take a bytecode file created by llvm-gcc on Unix, > move it to Windows, translate it to Intel syntax assembler, assemble it > with ML and expect it to work. You'll get an object file, but it won't > link. It used to work, but something changed to make the C runtime > libraries incompatible. lli cannot run the bytecode file either for the > same reason, nor will using CBE work anymore either. > > But for those of us writing our own front ends, this isn't a problem.I got the code I did from the mailing list. It needs some reworking as I created another TableGen identity. Its attached. If you can wait a week (as I am on another project at the moment) I will be able to do that. Aaron -------------- next part -------------- A non-text attachment was scrubbed... Name: MASM.tar.gz Type: application/x-gzip Size: 33434 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060502/b42b5420/attachment.bin>
Already committed yesterday. Aaron Gray wrote:>> Ok, less talk and more action. I just implemented proper Microsoft >> ML/MASM support. It probably has a few rough edges, so if anyone >> wants to try it out please do and let me know if you encounter any >> problems. >> >> Note that you cannot take a bytecode file created by llvm-gcc on >> Unix, move it to Windows, translate it to Intel syntax assembler, >> assemble it with ML and expect it to work. You'll get an object >> file, but it won't link. It used to work, but something changed to >> make the C runtime libraries incompatible. lli cannot run the >> bytecode file either for the same reason, nor will using CBE work >> anymore either. >> >> But for those of us writing our own front ends, this isn't a problem. > > I got the code I did from the mailing list. > > It needs some reworking as I created another TableGen identity. Its > attached. > > If you can wait a week (as I am on another project at the moment) I > will be able to do that. > > Aaron > ------------------------------------------------------------------------ > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
On Tue, 2 May 2006, Jeff Cohen wrote:>> I got the code I did from the mailing list. >> >> It needs some reworking as I created another TableGen identity. Its >> attached. >> >> If you can wait a week (as I am on another project at the moment) I will be >> able to do that.This looks different than what Jeff implemented, though he's far more of an expert on whether it is appropriate or not. One request though Aaron: instead of attaching a bunch of files like this, please attach a cvs diff against CVS head. This makes it much easier for us to apply the changes and understand what you changed. To get a diff, use something like this from the top level of your llvm tree: $ cvs diff -u If you have other unrelated changes, you can use: $ cvs diff -u lib/Target/X86/foo.cpp lib/Target/X86/blah.h ... Thanks, -Chris -- http://nondot.org/sabre/ http://llvm.org/