search for: x86compilationcallback_win64

...VM 3.3 using cmake/nmake, Microsoft C++ 2012, on a 64-bit Windows 7 system. I tried it with the 32-bit compiler as a test case first and that appeared to work, then with the 64-bit compiler in the hope that would give me a 64-bit build of LLVM, but instead got this error message: [ 86%] Generating X86CompilationCallback_Win64.obj Microsoft (R) Macro Assembler (x64) Version 11.00.51106.1 Copyright (C) Microsoft Corporation. All rights reserved. MASM : warning A4018:invalid command-line option : /llvm-3.3.src/lib/Target/X86/X86CompilationCallback_Win64.asm MASM : fatal error A1017:missing source filename NMAKE : fatal e...

...rosoft C++ 2012, on a > 64-bit Windows 7 system. I tried it with the 32-bit compiler as a test > case first and that appeared to work, then with the 64-bit compiler in > the hope that would give me a 64-bit build of LLVM, but instead got this > error message: > > [ 86%] Generating X86CompilationCallback_Win64.obj > Microsoft (R) Macro Assembler (x64) Version 11.00.51106.1 > Copyright (C) Microsoft Corporation. All rights reserved. > > MASM : warning A4018:invalid command-line option : > /llvm-3.3.src/lib/Target/X86/X86CompilationCallback_Win64.asm > MASM : fatal error A1017:missing so...

...rosoft C++ 2012, on a > 64-bit Windows 7 system. I tried it with the 32-bit compiler as a test case > first and that appeared to work, then with the 64-bit compiler in the hope > that would give me a 64-bit build of LLVM, but instead got this error > message: > > [ 86%] Generating X86CompilationCallback_Win64.obj > Microsoft (R) Macro Assembler (x64) Version 11.00.51106.1 > Copyright (C) Microsoft Corporation. All rights reserved. > > MASM : warning A4018:invalid command-line option : > /llvm-3.3.src/lib/Target/X86/X86CompilationCallback_Win64.asm > MASM : fatal error A1017:missing so...

...t;> 64-bit Windows 7 system. I tried it with the 32-bit compiler as a test case >> first and that appeared to work, then with the 64-bit compiler in the hope >> that would give me a 64-bit build of LLVM, but instead got this error >> message: >> >> [ 86%] Generating X86CompilationCallback_Win64.obj >> Microsoft (R) Macro Assembler (x64) Version 11.00.51106.1 >> Copyright (C) Microsoft Corporation. All rights reserved. >> >> MASM : warning A4018:invalid command-line option : >> /llvm-3.3.src/lib/Target/X86/X86CompilationCallback_Win64.asm >> MASM : fata...

...tLazyResolverFunction at X86JITInfo@llvm@@UEAAP6AXXZP6APEAXPEAX at Z@Z) 1>C:\llvm-2.7-src\build\bin\Release\Fibonacci.exe : fatal error LNK1120: 1 unresolved externals ========== Build: 0 succeeded, 1 failed, 22 up-to-date, 0 skipped ========== I'm not entirely convinced that lib/Target/X86/X86CompilationCallback_Win64.asm is being assembled and linked into that library - has anyone gotten this to link properly? thanks b

...ITInfo@llvm@@UEAAP6AXXZP6APEAXPEAX at Z@Z) > 1>C:\llvm-2.7-src\build\bin\Release\Fibonacci.exe : fatal error > LNK1120: 1 unresolved externals > ========== Build: 0 succeeded, 1 failed, 22 up-to-date, 0 skipped ========== > > I'm not entirely convinced that > lib/Target/X86/X86CompilationCallback_Win64.asm is being assembled and > linked into that library - has anyone gotten this to link properly? See if this bug report helps you to work around the problem: http://www.llvm.org/bugs/show_bug.cgi?id=4936 Please report your results.

...so where /INCLUDE:_foo was the right thing for 32-bit you seem to need /INCLUDE:foo for 64-bit. Manually editing the generated .vcproj file for llc got me past this error for now. The next problem I ran into is that the CMake-generated X86.vcproj project doesn't pull in the llvm/lib/Target/X86/X86CompilationCallback_Win64.asm file. I tried manually adding that file to the project. I must have screwed something up, though, because even though VS claimed to have found a custom build rule for .asm files, it gives a bunch of errors when trying to run the assembler. (Is it possible that it is applying the 32-bit assemble...