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

[Bug] Chapel compilation with rocm 6.2 hits LLVM assertion in developer builds #26424

Open
jabraham17 opened this issue Dec 17, 2024 · 2 comments

Comments

@jabraham17
Copy link
Member

Any Chapel compilation with ROCm 6.2 will hit an LLVM assertion.

third-party/llvm/install/linux64-x86_64/include/llvm/IR/GlobalValue.h:255: void llvm::GlobalValue::setVisibility(VisibilityTypes): Assertion `(!hasLocalLinkage() || V == DefaultVisibility) && "local linkage requires default visibility"' failed.

This occurs with CHPL_LLVM=bundled, CHPL_GPU=amd, CHPL_LOCALE_MODEL=gpu, and ROCm 6.2 being used. This is only an issue when the bundled LLVM was built with asserts on, either by CHPL_DEVELOPER being set in the environment or directly via make ASSERTS=1.

This should not effect most users, it should only effect developers

@jabraham17
Copy link
Member Author

Note: this seems to be a new issue with main that was not present in Chapel 2.2

@bonachea
Copy link
Contributor

This also currently affects Spack users building with chapel+rocm~developer, but that's due to a defect in the Spack recipe silently/incorrectly setting CHPL_DEVELOPER=false which is interpreted as enabling assertions in LLVM.

That defect in the Spack recipe is fixed in the Chapel 2.3 Spack PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants