diff options
| author | Albert Cheng <acheng@hdfgroup.org> | 2004-08-27 18:36:46 (GMT) |
|---|---|---|
| committer | Albert Cheng <acheng@hdfgroup.org> | 2004-08-27 18:36:46 (GMT) |
| commit | e2fa9d8da4eb8488062803c0568fe52ec2b3a91e (patch) | |
| tree | 212d275726a494e40242cb57f6033a01e947825b /test/h5test.c | |
| parent | 875f492181aa9e6e59661d0e679ca8e6c7a4f95c (diff) | |
| download | hdf5-e2fa9d8da4eb8488062803c0568fe52ec2b3a91e.zip hdf5-e2fa9d8da4eb8488062803c0568fe52ec2b3a91e.tar.gz hdf5-e2fa9d8da4eb8488062803c0568fe52ec2b3a91e.tar.bz2 | |
[svn-r9172] Purpose:
"bug fix" sort of.
Description:
The current mpicc at TG-NCSA recognizes uint64_t but not
int64_t. hdf5 code rightly assumes when the unsigned type
is defined, the corresponding signed type should be valid
too. So, when it detected uint64_t is valid, it went ahead
using int64_t which ended in compiling failure.
Solution:
Changed the detection to check on int64_t instead. This does
not change any logic, just goes around the mpicc compiler error
at TG-NCSA.
Platforms tested:
h5committested and tested at TG-NCSA (pp) too.
Misc. update:
Diffstat (limited to 'test/h5test.c')
0 files changed, 0 insertions, 0 deletions