[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #50510] 64-bit build issue
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #50510] 64-bit build issue |
Date: |
Wed, 22 Mar 2017 14:29:48 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #5, bug #50510 (project octave):
Ideally, the SuiteSparse_long type would be defined to be the same as int64_t,
and we wouldn't have to worry about this at all. But it sounds like macOS libc
defines int64_t to be "long long int", which seems unnecessary, but fine;
while SuiteSparse_long is just "long int".
I guess if we can't trust that SuiteSparse_long will always be the same as
int64_t on a given system, then we might need to introduce copying
(inefficient) or punning (maybe risky) to convert between what Octave uses for
64-bit integers and what SuiteSparse needs.
Or we add a configure rule to test that SuiteSparse_long is the same as
int64_t, and refuse to build against it if that is not the case.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50510>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/