-
-
Notifications
You must be signed in to change notification settings - Fork 489
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 linbox solve for sparse matrices #26178
Comments
This comment has been minimized.
This comment has been minimized.
Upstream: Reported upstream. No feedback yet. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:6
setting this to positive |
comment:7
Presuming these are all correctly reviewed as either duplicate, invalid, or wontfix. |
This was referenced Dec 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
All the issues had been treated in #23214 which get rids of the sage-linbox interface.
While cleaning the linbox interface at #24544 we encountered some issues with an innocent type change. The sage-linbox interface is using
LinBox::DenseVector<Givaro::Modular<unsigned int>>
while it would be more natural to deal withGivaro::Modular<int64_t>
orGivaro::Modular<uint64_t>
. Though some strange compilation failures were present on macOS X, see discussion from the discussion at #24544.Once this is fixed, we could get rid of the sage-linbox interface.
This problem is also tracked in linbox at issue 117.
Upstream: Reported upstream. No feedback yet.
CC: @ClementPernet @fchapoton
Component: interfaces
Issue created by migration from https://trac.sagemath.org/ticket/26178
The text was updated successfully, but these errors were encountered: