-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
clang 15 changed symbol mangling and might produce backwards incompatible binaries #213
Comments
How big is the blast radius here? Do you want to use the compat ABI? Do we need a full-blown compiler migration just to get everything onto the new mangling? |
It's only one feedstock for now. Not sure how widespread it will be. |
Given that this issues doesn't seem to have a wide blast radius, shouldn't we simply recompile givaro and its dependents with LLVM 15? |
That will break old downstream packages depending on older ABI. |
That's what I meant with rebuilding its dependent packages (like a migration). Or do you mean consumers outside of conda-forge? I don't think we should just keep blocking things like conda-forge/compilers-feedstock#57 (or the next clang upgrade) indefinitely. The options I can imagine are:
Maybe I'm overlooking something? |
I sent PRs to keep givaro and its dependencies (through pkg-config file) with |
Yes, I saw, which is why I said "keep givaro on...". Is this your preferred long-term solution? Does it remove your hold on conda-forge/compilers-feedstock#57? |
See https://releases.llvm.org/15.0.0/tools/clang/docs/ReleaseNotes.html#id5
Mangled symbol changed from
to
The text was updated successfully, but these errors were encountered: