-
-
Notifications
You must be signed in to change notification settings - Fork 346
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
Add support for SUNDIALS 5.5-5.7 compiled with LAPACK #1004
Conversation
0bdf8f7
to
797f740
Compare
Codecov Report
@@ Coverage Diff @@
## main #1004 +/- ##
==========================================
- Coverage 70.67% 70.66% -0.02%
==========================================
Files 362 361 -1
Lines 44554 44522 -32
==========================================
- Hits 31488 31460 -28
+ Misses 13066 13062 -4
Continue to review full report at Codecov.
|
797f740
to
4de1ba8
Compare
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.
Per my comments elsewhere, this isn't necessarily my strong suit (and I don't have the toolchains to verify this installed). On the other hand, both PR rationale and code comments are clear and the changes appear to be straightforward. Testing every combination in GH Actions may be overkill, but if there are candidates of particular concern this may be warranted. Overall, no concerns from my side ...
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.
This looks good from a functional standpoint. I just have a couple of requests on the formatting.
If CT_USE_LAPACK is false, then CT_SUNDIALS_USE_LAPACK is also always false. Thus the CT_SUNDIALS_USE_LAPACK branch here was never being exercised.
In SUNDIALS >= 5.5, there is no longer a define that indicates SUNDIALS was compiled with LAPACK globally. Instead, the specific SUNLINSOL libraries that actually use LAPACK are listed explicitly.
SUNDIALS 4.0 deprecated the SUNSPGMR function name, replacing it with a more specific version. The more specific version isn't available in SUNDIALS 3.0 though, so we need another check here.
It is possible for the OMP header to be installed in the search path, but the library not to be available. This can happen, for example on macOS when Boost and GCC are installed by Homebrew, the Homebrew include path is set to find Boost, and the Apple compilers are being used.
df44b7c
to
e379b6d
Compare
Changes proposed in this pull request
BandMatrix.cpp
omp.h
is installed, but the library cannot be found by the linker (for example, omp installed by Homebrew, the Homebrew path on the search path, but using Apple's compilers).Checklist
scons build
&scons test
) and unit tests address code coverage