-
Notifications
You must be signed in to change notification settings - Fork 262
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
SuiteSparse 7.7.0 #778
Merged
Merged
SuiteSparse 7.7.0 #778
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lesky & Backslash)
…backend. There are different versions of Clang on Windows: Some of those versions use a GNU-compatible command line interface. Other versions use a MSVC-compatible command line interface (`clang-cl`). Additionally, either of those versions could use a MSVC-compatible backend or a MinGW-compatible backend. CMake sets the MSVC variable if the compiler uses a MSVC-compatible command line interface *and* a MSVC-compatible backend. The naming convention for import libraries differs between the MSVC-compatible (`.lib`) and MinGW-compatible backends (`.dll.a`). Use the same naming conventions for static libraries that are used for MSVC also for the Clang that uses a GNU-compatible command line interface but a MSVC-compatible backend. This should be fixing #749.
For `clang-cl`, both `_MSC_VER` and `__clang__` are set. Move check for `_MSC_VER` to before check for `__clang__` to allow identifying `clang-cl` as a MSVC compatible compiler.
ParU depends on UMFPACK. Add rules to automatically add UMFPACK to the list of packages to be built if ParU is selected unless `SUITESPARSE_USE_SYSTEM_UMFPACK` is set.
CMake: Use MSVC naming convention for compilers that simulate a MSVC backend.
GraphBLAS: Correctly identify `clang-cl` as MSVC-compatible compiler
GraphBLAS: Avoid possibility of compatible types in `_Generic` selections
Root CMakeLists.txt: Automatically pull in UMFPACK when building ParU.
Fix SPEX for 32-bit platforms
Document `SUITESPARSE_C_TO_FORTRAN` in `README.md`
…RSE_C_TO_FORTRAN instead, with better docs
ParU: Explicitly include <cinttypes> in header that uses `PRId64`
SPEX User guide update
Updated to 2024 Homogenized all names, and orders.
Copyright Updates
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.