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

[0.6] LLVM intrinsics are looked up in the wrong place #23009

Closed
Keno opened this issue Jul 28, 2017 · 4 comments
Closed

[0.6] LLVM intrinsics are looked up in the wrong place #23009

Keno opened this issue Jul 28, 2017 · 4 comments

Comments

@Keno
Copy link
Member

Keno commented Jul 28, 2017

See e.g. https://ci.appveyor.com/project/Keno/pyjulia/build/1.0.15/job/mtc9w4vf23l0nu5y. When llvm lowers intrinsics to libcalls, it apparently tries looking them up in the base executable, which doesn't have them. We should either do look them up in openlibm or, even better, do something like #18927.

@vtjnash
Copy link
Member

vtjnash commented Jul 28, 2017

It should have them? We statically link libopenlibm into most places to make sure this works.

@vchuravy
Copy link
Member

Since #18927 is uncertain #16066 might be the more actionable approach.

@KristofferC
Copy link
Member

@Keno, anything left to do here?

@Keno
Copy link
Member Author

Keno commented Dec 30, 2020

There is a more generalized problem about communicating with LLVM about libcalls, but I think this particular issue is resolved. A new issue can be filed with a reproducer when this issue rears its head again.

@Keno Keno closed this as completed Dec 30, 2020
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

4 participants