Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Codegen/SBF/vararg1.ll fails #101

Closed
ripatel-fd opened this issue Jul 4, 2024 · 1 comment
Closed

Codegen/SBF/vararg1.ll fails #101

ripatel-fd opened this issue Jul 4, 2024 · 1 comment

Comments

@ripatel-fd
Copy link

To reproduce:

llvm-lit -v llvm/test/CodeGen/SBF/vararg1.ll
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.

@ripatel-fd
Copy link
Author

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.

@ripatel-fd ripatel-fd closed this as not planned Won't fix, can't repro, duplicate, stale Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant