[LLVMdev] Win32 COFF Support

Nathan Jeffords blunted2night at gmail.com
Wed Jun 9 20:11:51 PDT 2010

This is cool, I was looking into something like this, but hit a little bit
of a wall, and then got sidetracked on another project. I was going to use
llc to generate COFF object files as opposed to clang. Seems to me llc would
give better control over what was generated and would also not require clang
to be in the tree.

Is there any documentation on how to run these tests from windows?

- Nathan

On Wed, Jun 9, 2010 at 3:15 PM, Bigcheese <bigcheesegs at gmail.com> wrote:

> On Fri, May 28, 2010 at 4:28 PM, Eli Friedman <eli.friedman at gmail.com>
> wrote:
> > > Any objections for not accepting the patch into LLVM? If none, I'll
> > > apply it after the weekend.
> >
> > There should minimally be a bare-bones test to make sure that basic
> > COFF writer functionality doesn't crash.  Besides that, I don't see
> > any issues.
> I was looking into writing this test for MC based on the MachO tests,
> but llvm-mc cannot read .s files as COFF because it simply lacks
> support for it. It tries to read everything as MachO.
> I've attached a patch for the test anyway. This includes Nathan's
> dump-coff.py script in the proper location for the test. I generated
> the .s file with "echo int main(){} | clang -O3 -S -x c -o - -". And
> then I generated the CHECK lines by running "echo int main(){} | clang
> -O3 -c -x c -o temp.o - && dump-coff temp.o".
> - Michael Spencer
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100609/0cadaabe/attachment.html>

More information about the llvm-dev mailing list