Displaying 4 results from an estimated 4 matches for "enable_ffi".
Did you mean:
enable_fd
2015 Jul 28
0
[LLVMdev] Regression testing on MSYS2 host with mingw-w64
This test results in UNSUPPORTED on my system, since config.enable_ffi =
"OFF". This is the result of LLVM_ENABLE_FFI which is OFF by default. Is it
turned ON in your build?
2015-07-28 17:32 GMT+03:00 Martell Malone <martellmalone at gmail.com>:
> Hi Yaron,
>
> I know you sent me some emails before about regression testing on MSYS2
> So...
2015 Jul 28
2
[LLVMdev] Regression testing on MSYS2 host with mingw-w64
Hi Yaron,
I know you sent me some emails before about regression testing on MSYS2
So you might have some idea about this
I am getting a regression error on check-llvm.
With the llvm/trunk/test/ExecutionEngine/Interpreter/intrinsics.ll
FAIL: LLVM :: ExecutionEngine/Interpreter/intrinsics.ll (7635 of 14266)
> ******************** TEST 'LLVM ::
>
2015 Jul 28
2
[LLVMdev] Regression testing on MSYS2 host with mingw-w64
...GS}" \
> -DCMAKE_INSTALL_PREFIX=/mingw64 \
> -DCMAKE_BUILD_TYPE=Release \
> -DLLVM_TARGETS_TO_BUILD="ARM;AArch64;CppBackend;X86" \
> -DLLVM_ENABLE_ASSERTIONS=OFF \
> -DLLVM_ENABLE_THREADS=0 \
> -DPYTHON_EXECUTABLE=/mingw64/bin/python2.exe \
> -DLLVM_ENABLE_FFI=ON \
> -DLLVM_ENABLE_SPHINX=ON \
> ../llvm
>
Is this not supported?
We do have a build of libffi in mingw-w64 and it works well with other
projects.
On Tue, Jul 28, 2015 at 6:49 PM, Yaron Keren <yaron.keren at gmail.com> wrote:
> This test results in UNSUPPORTED on my syst...
2015 Jul 28
0
[LLVMdev] Regression testing on MSYS2 host with mingw-w64
...KE_INSTALL_PREFIX=/mingw64 \
>> -DCMAKE_BUILD_TYPE=Release \
>> -DLLVM_TARGETS_TO_BUILD="ARM;AArch64;CppBackend;X86" \
>> -DLLVM_ENABLE_ASSERTIONS=OFF \
>> -DLLVM_ENABLE_THREADS=0 \
>> -DPYTHON_EXECUTABLE=/mingw64/bin/python2.exe \
>> -DLLVM_ENABLE_FFI=ON \
>> -DLLVM_ENABLE_SPHINX=ON \
>> ../llvm
>>
>
> Is this not supported?
> We do have a build of libffi in mingw-w64 and it works well with other
> projects.
>
>
On Tue, Jul 28, 2015 at 6:49 PM, Yaron Keren <yaron.keren at gmail.com> wrote:
> This...