You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FAIL: LLVM :: CodeGen/SBF/vararg1.ll (1 of 50241)
******************** TEST 'LLVM :: CodeGen/SBF/vararg1.ll' FAILED ********************
Script:
--
: 'RUN: at line 1'; not /data/ripatel/llvm-project/build/bin/llc -march=sbf < /data/ripatel/llvm-project/llvm/test/CodeGen/SBF/vararg1.ll 2> /data/ripatel/llvm-project/build/test/CodeGen/SBF/Output/vararg1.ll.tmp1
: 'RUN: at line 2'; /data/ripatel/llvm-project/build/bin/FileCheck /data/ripatel/llvm-project/llvm/test/CodeGen/SBF/vararg1.ll < /data/ripatel/llvm-project/build/test/CodeGen/SBF/Output/vararg1.ll.tmp1
--
Exit Code: 1
This test seems to assert that the compiler prints the error message "Functions with VarArgs are not supported".
However, on my machine, the abort signal generated by the compiler crashes the unit test. Maybe we should generate a more graceful error message than an abort.
The text was updated successfully, but these errors were encountered:
This was because the not binary came from a different LLVM installation (system LLVM). It behaves subtly different than the project LLVM. The fix is to install the toolchain to a staging dir and point PATH to it.
To reproduce:
This test seems to assert that the compiler prints the error message "Functions with VarArgs are not supported".
However, on my machine, the abort signal generated by the compiler crashes the unit test. Maybe we should generate a more graceful error message than an abort.
The text was updated successfully, but these errors were encountered: