diff options
author | Albert Cheng <acheng@hdfgroup.org> | 2004-08-05 05:15:08 (GMT) |
---|---|---|
committer | Albert Cheng <acheng@hdfgroup.org> | 2004-08-05 05:15:08 (GMT) |
commit | 5390a63a77772ef0f91a0fd286128be9d5a84e8c (patch) | |
tree | ba9dbc00c5c69fc2ffc0f4957f661fff03440c37 /tools/h5jam/tellub.c | |
parent | a5bd3e42ea0913d6b652c26f82bd688ed6741cd1 (diff) | |
download | hdf5-5390a63a77772ef0f91a0fd286128be9d5a84e8c.zip hdf5-5390a63a77772ef0f91a0fd286128be9d5a84e8c.tar.gz hdf5-5390a63a77772ef0f91a0fd286128be9d5a84e8c.tar.bz2 |
[svn-r9018] Purpose:
Bug fix (Failures when dataset size >= 1 GB, reported by Bill Loewe.)
Description:
In the IBM AIX system using 32bit mode, if a dataset size was 1GB or
larger, when the "end" of the dataset was selected, MPI would complain
it could not keep the Upper bound of a datatype within the range of
MPI_Aint. This was because the old algorithm would derive the selection
with extent of each row first. After all dimensions were processed,
it then calculate the start position and just displace the whole
MPI derived type. So, the final MPI type was actually the start
position plus the whole dataset. Since the start can be as big as
the whole dataset, this made the final derived twice as big as 1GB.
That would hit the 2GB MPI_Aint range limit in the 32 bit mode.
Solution:
Use a different algorithm to include the start position in the
defining of MPI type for each dimension. When all dimensions
are processed, the MPI type represents the selection exactly.
Platforms tested:
h5committested
Misc. update:
Diffstat (limited to 'tools/h5jam/tellub.c')
0 files changed, 0 insertions, 0 deletions