[LLVMdev] GCC assembler rejects native code generated by LLVM
reid at x10sys.com
Mon Mar 7 16:39:19 PST 2005
Just to add a little more to this discussion ...
As part of the Cygwin port I was doing, I managed to get a similar (or
possibly exactly) the same symptom: assembly output was using keywords
or extensions that the GNU assembler didn't recognize. This was caused
by using the wrong assembly style (intel vs. at&t). To get this to work
correctly, I had to teach LLVM that for "cygwin" platforms it should
generate at&t style x86 assembly. The same simple change might fix the
problem for mingw .. or this could be a red herring. I'll comment again
on this once I see the output from Vyacheslav ..
On Mon, 2005-03-07 at 08:57, Vyacheslav Akhmechet wrote:
> > I'm confused. My understanding is that Visual C++ Express does not
> > include Visual Studio, which is required to build LLVM.
> Well, Visual C++ Express is a cut down version of Visual Studio. I'm
> not sure about exact differences between editions but Visual C++
> Express does read the .sln files and comes with an excellent C++
> compiler. I didn't encounter any problems building llvm or running
> various tools.
> > Anyway,
> > assembly code generation is not yet supported using the Microsoft tool
> > chain (as documented in the Getting Started with VS page)
> I've seen that document. It suggests that one cannot assemble native
> executables using MS tools because they don't come with an assembler.
> Another document (don't remember which one, exactly) says native code
> generation is supported on Windows using Mingw tools. This is exactly
> what I'm trying to do: assemble an executable using Mingw. I don't see
> why it should matter whether llvm tools are built using gcc or MSVC,
> the generated assembly code should be the same, shouldn't it?
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: This is a digitally signed message part
More information about the llvm-dev