-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix version symbol problem #10
Comments
I'm debugging this and I leave some memo here. I temporarily revives the CHECKs disabled in #6 and ran In all failures, the symbols were In Line 32 in 8430ecd
I tracked Line 105 in 8430ecd
At first, SymtabBuilder::Resolve was called with the second versym 6 is copied from the first versym, but where did the first versym come from? Other symbols processed by this line all had nonempty soname and version So I changed Line 88 in 8430ecd
to
and ninja succeeded (I don't know why) |
|
|
In my case, with this fix 5ac192f,
|
thanks! (below is memo for myself) the versym is 65535, which is NO_VERSION_INFO, set at Line 198 in f7ea7ea
I updated bool is_special_ver_ndx(Elf64_Versym versym) {
return (versym == VER_NDX_LOCAL || versym == VER_NDX_GLOBAL || versym == NO_VERSION_INFO);
} and now feature_unit_tests passes in python3.8/ubuntu20.04. Still, cuBLASLt and cuBLAS-related tests are failing in python3.8/ubuntu20.04 and I continue investigation |
We fail to handle the default version symbol now. But not sure.
https://github.com/pfnet/sold/pull/6/files#diff-ea346e7232da277fcbfd75eb0102ceed1fca1e6c180b2bd4f64d40773c83717bR527
The text was updated successfully, but these errors were encountered: