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
[Misc] [refactor] Move symbol versioning to a new file #3426
Conversation
✔️ Deploy Preview for jovial-fermat-aa59dc canceled. 🔨 Explore the source changes: e151e1e 🔍 Inspect the deploy log: https://app.netlify.com/sites/jovial-fermat-aa59dc/deploys/61967b393454900007deacd4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we also add link to the issue in both files? ;)
you mean link to this issue? #3174 |
@qiao-bo Yup either issue or PR or a short note describing the problem it's trying to solve will help a lot! Thanks! |
/format |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job, LGTM!
/format |
@k-ye @ailzhang, The GLIBC 2.2.5 still cannot be used at the moment due to Vulkan. Nevertheless, this PR also moves the symbol version code to a new file and i think this part can be merged. I renamed it and opened a new issue #3552 to track next steps when we have time in the future. what do you think? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Create a new
symbol_version.cpp
for pinning math symbols to older GLIBC versions.This PR also documents the method to pin offending math symbols back to GLIBC 2.2.5:
Related issue = #3174
Reference solution: #1342
Taichi build on a Ubuntu 20.04
Before:
After:
objdump -T libtaichi_core.so | grep GLIBC_2.29
gives none. current glibc versioning is