Displaying 7 results from an estimated 7 matches for "llvmvar".
Did you mean:
llvmvars
2010 Jan 21
2
[LLVMdev] how to compile asm output for x86 with Micorsoft's ML
I was recently trying to compile some bitcode generated like so:
llc --x86-asm-syntax=intel test.out
it generates a test.out.s file, and while I'm not much of an assembly
person, it looks OK. When I feed this to ML
ml test.out.s
I get tons of errors, most of which appear to be syntax errors. Stuff like:
test.out.s(2) : error A2008:syntax error : .
error A2008:syntax error :
2010 Jan 21
0
[LLVMdev] how to compile asm output for x86 with Micorsoft's ML
...d target 'c'.
[snip]
> Registered Targets:
> x86 - 32-bit X86: Pentium-Pro and above
> x86-64 - 64-bit X86: EM64T and AMD64
By default, the cmake build generates Visual Studio project files for
the X86 target only. Take a look at
http://www.llvm.org/docs/CMake.html#llvmvars
for learning how to build other targets.
IIRC, the C target is named CBackend.
2010 Jan 21
2
[LLVMdev] how to compile asm output for x86 with Micorsoft's ML
> By default, the cmake build generates Visual Studio project files for
> the X86 target only. Take a look at
>
> http://www.llvm.org/docs/CMake.html#llvmvars
>
> for learning how to build other targets.
OK thanks, I'll look at that.
In the meantime, is it possible to get the assembly generated by llc
to work wiht ML? That would probably be the ideal solution.
Cheers
Jim
2010 Jan 21
0
[LLVMdev] how to compile asm output for x86 with Micorsoft's ML
On Jan 21, 2010, at 12:54 PM, Jim Crafton wrote:
>> By default, the cmake build generates Visual Studio project files for
>> the X86 target only. Take a look at
>>
>> http://www.llvm.org/docs/CMake.html#llvmvars
>>
>> for learning how to build other targets.
>
> OK thanks, I'll look at that.
>
> In the meantime, is it possible to get the assembly generated by llc
> to work wiht ML? That would probably be the ideal solution.
Nope, llvm's .s output is only compatible with...
2010 Oct 18
2
[LLVMdev] building only libs with cmake
Hi!
is it possible to build only the libs (and no executables) with cmake?
I already have LLVM_BUILD_TOOLS:BOOL=OFF
and CLANG_BUILD_EXAMPLES:BOOL=OFF but things like Kaledoscope
are still built.
-Jochen
2010 Oct 18
0
[LLVMdev] building only libs with cmake
...y at arcor.de> writes:
> is it possible to build only the libs (and no executables) with cmake?
> I already have LLVM_BUILD_TOOLS:BOOL=OFF
> and CLANG_BUILD_EXAMPLES:BOOL=OFF but things like Kaledoscope
> are still built.
LLVM_BUILD_EXAMPLES=OFF
http://www.llvm.org/docs/CMake.html#llvmvars
2009 Dec 17
1
[LLVMdev] LLVM MinGW binaries on Vista issue
Hello, Jon
> To make it easier to use the LLVM-GCC MinGW32 binary and meet your GPL licensing requirements, could you embed the MinGW binutils binary as-is in the LLVM-GCC MinGW32 and update the LLVM docs to point to the MinGW SourceForge download site for those wanting the MinGW binutils source?
I still don't think it's good idea. binutils will add something like
10Mb to package