| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Remove H5_MPI_SPECIAL_COLLECTIVE_IO_WORKS and
H5_MPI_COMPLEX_DERIVED_DATATYPE_WORKS #defines from source.
Description:
Two advanced parallel functionalities, special collective IO and
complex derived datatypes, are not supported by older
implementations of mpi, and thus our code limits the use of these
features with #ifdefs and has checks in configure to set them (or
not). Unfortunately, configure can't actually run a parallel check
to see if these features are working (nor not) so it resorts to
looking in the config files where they are explicity enabled or
disabled based on versions of mpi, sytems being built on, or for
no documented reason at all (i.e. just set to on or off as some
'default'). Overriding these settings is easy if need be, provided
it is known that it needs to be done to get improved performance,
and oftentimes it is not.
Most new MPI implementations successfully handle the functionality
requested when these #defines are set, and many of the "turn these
features off" cases in the config files are for old (> 5 years)
versions of MPI and retired systems (such as NCSA's tungsten).
Therefore, the decision has been made to remove the support for
these old versions of MPI and systems that cannot handle these
behaviors. The #ifdefs and supporting setup in the config/ files
and configure script has been removed, and the code executed when
these options were not set removed from the source.
In passing, this commit also cleans up some whitespace issues in
both t_mpi.c and H5Dmpio.c. Furthermore, in t_mpi.c, the special
collective IO test was not getting regularly run due to it being
written to work only with four processes (we regularly test with
six, previously with three), and thus it failed when actually run
due to an out of bounds data buffer assignment. It has been
modified to run at any number of processes greater than four, and
the memory problem has been fixed so the test passes.
Tested:
jam, h5committest, ember
|
|
|
|
|
|
| |
H5_SIZEOF_LONG_LONG. This is set if 64-bit integers are supported.
Tested: local linux
|
| |
|
| |
|
|
|
|
| |
creates it.
|
|
|
|
| |
rather then in one group. Discovered from public 1.8 CDash reports.
|
|
|
|
| |
public 1.8 CDash reports
|
|
|
|
|
|
|
|
|
|
|
|
| |
Work for HDFFV-7600 - GMQS: h5diff - argument options -d, -p and --use-system-epsilon should be mutually exclusive.
Description:
Fixed h5diff to display instructive error message and exit with 1
when mutually exclusive options (-d, -p and --use-system-epsilon)
are used together.
Tested:
jam (linux32-LE), koala (linux64-LE), heiwa (linuxppc64-BE), tejeda (mac32-LE), linew (solaris-BE), Cmake (jam)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix HDFFV-7522
"--enable-production=xxx will produce incorrect configure summary"
Description:
Fixed a typo in configure.in that resulted in "-enableval" being
displayed by the configure summary (and set in the CONFIG_MODE
makefile variable) if the production mode was set to anything other
than yes, no, or profile. The summary and CONFIG_MODE variable will
now be set to the value specified by the user.
Tested:
jam, h5committest
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tweak make_vers script so that it indents preprocessor commands inside
#ifdefs, is more forgiving and informative about the input file's prefix, and
is better parameterized with the global variables at the beginning of the
script. When major versions are branched from the trunk, the $max_idx value
should be the only value that needs to be changed in the version of the script
on the trunk.
Changes to H5version.h file are just indention.
Tested on:
Mac OS X/32 10.6.8 (amazon)
(too minor to require h5committest)
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Work for HDFFV-7602 - HDF5 command tools: Provide framework for reusable
test files among tools
Description:
Provide framework to share test files among tools for tools test.
Tested:
jam (linux32-LE), koala (linux64-LE), heiwa (linuxppc64-BE)
|
| |
|
|
|
|
| |
Tested: windows
|
| |
|
| |
|
|
|
|
|
|
| |
2594). According to Quincey's suggestion, I moved the EOAs for individual files from H5FD_multi_fapl_t to H5FD_multi_t struct. It's a more proper place.
Tested on jam, koala, and heiwa.
|
|
|
|
|
|
|
|
| |
Changed the length of the fortran string passed to HD5packFstring in the function nh5pget_external_c. The 3rd
argument should be the fortran length of the string, not the C length of the string (which includes the null).
Tested: jam (intel and gnu), also checked the example h5ex_d_extern.f90 which detected the problem on Amazon c2
machine (reported by Larry).
|
|
|
|
|
|
| |
status of check
Tested: heiwa
|
|
|
|
|
|
|
|
| |
2598). I added two minor changes: 1. put the output file for
vfd.c test in the list for cleanup in Makefile.am; 2. put the data file in the list in CMakeLists.txt.
Tested on jam - simple change.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
whole MULTI file saved in the
super block. We took it out in v1.8 library because it's meaningless
for the MULTI file. v1.8 library saves the EOA for the metadata file,
instead. But this caused some backward compatibility problem.
v1.8 library couldn't open the file created with v1.6 library. I
fixed the problem by checking the EOA value to detect the file
created with v1.6 library.
Tested on jam, koala, and heiwa.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
HDFFV-5878 - GMQS: h5dump - incorrect output format for array type with multiple elements in an index
Description:
Fixed h5dump to display the first line of each element into correct
position for multiple dimention array type.
Before this fix, the first line of each element in array were displayed
after the last line of previous element without moving to the next
line (+indentation)
Tested:
jam (linux32-LE), koala (linux64-LE), heiwa (linuxppc64-BE), tejeda (mac32-LE), linew (solaris-BE), Windows (32-LE)
|
|
|
|
|
|
| |
inside the test macro. Allows individual tests to be independently executed.
Tested: local linux
|
|
|
|
|
|
| |
Added Fortran example for HL DS APIs.
Tested: jam (intel)
|
| |
|
| |
|
|
|
|
| |
Tested: Debug windows
|
|
|
|
|
|
|
|
| |
many times. VMS can't handle it. We need a solution in
the future. Please see Issue 7620 in Jira about it.
Not tested yet.
|
|
|
|
|
|
| |
`date` form.
Tested: Jam by running bin/release and eyeballed the new date format.
|
|
|
|
|
|
| |
old one [...] had problem.
Tested 1.8 on VMS.
|
|
|
|
|
|
| |
say which filter isn't registered. This is the follow-up commit. The previous way to construct the name of the existent data file wasn't very safe. It could be cleaned up if any user builds the library in the source directory.
Tested on jam - simple change.
|
|
|
|
|
|
| |
Added new test and test files to test section
Tested: local linux
|
| |
|
|
|
|
| |
Tested: jam (intel, gnu, pgi)
|
|
|
|
|
|
|
|
| |
say which filter isn't registered. This is the follow-up commit. In my first checkin, I took out the line "H5Z_SZIP->encoder_present = SZ_encoder_enabled()" by
mistake. It caused SZIP test to fail. I'm puting it back now.
Tested on jam - simple change.
|
|
|
|
|
|
| |
say which filter isn't registered. This is the follow-up commit. In my previous commit, I changed HDsnprintf to snprintf, which caused trouble for Windows because the name is _snprintf instead. So I changed it back to HDsnprintf for properly defined macro. I also changed all fprintf to HDprintf to be consistent.
Tested on jam - simple change.
|
| |
|
|
|
|
|
|
|
| |
Added additional attaching and detaching permutation.
Tested:
jam (intel, gnu)
|
|
|
|
|
|
|
|
| |
say which filter isn't registered. This is the follow-up commit (20929 and 20930). The check-vfd in Makefile has trouble with the file name. Because the test file
is pre-generated, I use the default FAPL to create the full file name to avoid some driver test.
Tested on jam - simple change.
|
|
|
|
|
|
|
| |
say which filter isn't registered. This is the follow-up commit. When I checked in the fix and test (revision 20929), I forgot to add the data file test/filter_error.h5.
I've tested it in my previous checkin.
|
|
|
|
|
|
| |
say which filter isn't registered. The fix is simple. Most of the effort is on the test. The file with filter enabled is created in gen_filter.c. The verification of the error message is in test_error.c. The output is compared against the standard output.
Tested on jam, koala, and heiwa.
|
|
|
|
|
|
|
|
|
|
|
| |
HDFFV-7607: h5ls - improve efficiency of test scripts - removing top 3 extra lines from expected output files
Description:
This is a subtask from 'HDFFV-7514 - gmqs: h5dump - improve effectiveness of testing scripts for handling expected output files'.
This is prerequisite for 'HDFFV-7602 tools - upgrade tools' test scripts to share test files among tools, providing framework for test file re-usability.'
Tested:
jam (linux32-LE), koala (linux64-LE), heiwa (linuxppc64-BE), tejeda (mac32-LE), linew (solaris-BE), Windows (32-LE), Cmake (jam)
|
|
|
|
|
|
| |
detaching DS, see bug HDFFV-7605.
Tested: Jam (intel and gnu)
|
| |
|
|
|
|
|
|
| |
took out the error report for 2 H5Tclose calls in H5T_conv_enum because they would clear the error stack.
Tested on jam - simple change.
|
|
|
|
|
|
|
|
|
|
| |
When no conversion is involved in reading or writing the
data, overflowing values are retained. When conversion happens, the values become -1. The conversion function puts -1
when overflow happens. I added two new dataset transfer property to control whether to fill 0xff in the destination
data or convert to the destination data when overflow happens. The two new functions are H5Pset(get)_enum_conv_overflow. I also added test cases in enum.c and dtypes.c.
Tested on jam, koala, and heiwa.
|
| |
|
|
|
|
| |
comparision of code changes
|
|
|
|
|
|
|
|
| |
This was to solve an issue of a difference between 1.8 and trunk. 1.8 used the wrong variable in the if() and upon reflection the if() was determined to be unnecessary and complicated the logic. 1.8 tests would have treated the if() as always true with the result being the same as though the if() was absent.
This change reflects that equivalance and will avoid a potential problem in 1.8.
Tested: local linux, reviewed by two developers
|
| |
|