-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
39516b6
commit df2eff3
Showing
2 changed files
with
33 additions
and
33 deletions.
There are no files selected for viewing
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
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
df2eff3
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 completely backwards
df2eff3
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.
The
SuiteSparse_long
is similar to ourInt
, i.e. determined by the architecture. On 64 bit, CHOLMOD and UMFPACK let you useCint/Int32
for the integers, but this option is not there for SPQR which call the_l_
versions of the functions. On 32 bit there is really no difference between the_l_
and the non-_l_
version, but they cannot be mixed so therefore I had to change our default such that we now call the_l_
versions whenever the chosen integer type is the same asInt
. Does it make sense?df2eff3
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.
I think so, but please include this kind of information in the commit message, comments, or both.
Mostly. It's set to
long
on all architectures except for Win64, where it's set to__int64
. I don't believe we're overwriting this behavior anywhere.df2eff3
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.
Isn't our
Int
always a 32 bit integer type on 32 bit systems and a 64 bit integer type on 64 bit systems just likeSuiteSparse_long
? I believe I'm relying on this assumption in thecholmod_name
macro.df2eff3
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.
With the default configuration of suitesparse, yes. However when we're using system versions of this library we're at the mercy of how suitesparse was configured. I'd prefer we make as few assumptions as possible, and rely on the information that we actually get from the library (our wrapper, anyway) about how it was configured.
df2eff3
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.
Okay. Thanks for the comments. I've changed the dependence on
Int
toSuiteSparse_long
which is detected from the linked library. I'll push as soon as the tests pass locally.df2eff3
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 is certainly a better way to go about it.