| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
H5D_CHUNK_CACHE_NSLOTS_DEFAULT_F
H5D_CHUNK_CACHE_NBYTES_DEFAULT_F
H5D_CHUNK_CACHE_W0_DEFAULT_F
to
H5D_CHUNK_CACHE_NSLOTS_DFLT_F
H5D_CHUNK_CACHE_NBYTES_DFLT_F
H5D_CHUNK_CACHE_W0_DFLT_F
to get under the 31 limit for variable names
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Updated bin/reconfigure to use latest version of automake (1.10.2).
Re-generated Makefile.in's by running bin/reconfigure.
- Added libtool version numbers to c++, fortran, hl, hl c++, and hl fortran
libraries.
Tested:
jam, liberty, smirom
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added tests for the new APIs:
H5D_H5DGET_ACCESS_PLIST_F
H5I_H5IIS_VALID_F
H5P_H5PSET_CHUNK_CACHE_F
H5P_H5PGET_CHUNK_CACHE_F
Platforms tested:
smirom: pgf90, ifort
linew
liberty: gcc43, gfortran43, gcc44, gfortran44
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
Fixing BZ #1381. The --includedir=DIR configure option, which is used
to specify the installation location of C header files, did not work
correctly as the path was hard-coded in config/commence.am. I'm presuming
this is because an older version of automake didn't know where to put
c header files. In any case, removing this line now defaults the includedir
to the same directory that it is currently hard-coded to, and also fixes
the configure flag to allow customization of this value.
Tested:
jam, liberty
|
|
|
|
|
|
|
| |
big or little endian machine. Configure.in was modified to export a variable carrying endianess information to testh5ls.sh. This script then compares the current run with 2 expected outputs, one for a big-endian machine (linew was used to generate the output), other for little endian (jam was used to generate the output)
the way h5ls prints types, it starts searching for NATIVE types first. One solution would be h5ls not to detect these native types, using for example the same print datatype function that h5dump does, that would make the output look the same on all platforms ("32-bit little-endian integer" would be printed instead). Drawback, this "native" information would not be available. Other solution is to have not one but 2 expected outputs and make the shell script detect the endianess and compare with one output or other
tested: h5committest
|
|
|
|
|
|
|
| |
Cosmetic changes, Also tested -r16231 on:
Jam (intel 10.1)
Smirom (intel 10.1)
|
|
|
|
| |
Added chunk property to the data set because changes in the cC function H5Dset_extent now require/check that the data set is chunked.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
- Remove need to set LD_LIBRARY_PATH when using shared szip library.
- Libtool 2.2.6a is now used to generate libraries.
- 'make check install' dependency bug is fixed, and should no longer
break the build.
- removed hard coding of shell in config/commence.am, as this causes
problems on Solaris with the new version of libtool.
- RELEASE.txt with appropriate changes.
Tested:
- kagiso, smirom, linew (merged from 1.8, pretty quick tests)
|
|
|
|
| |
Removed blank lines
|
|
|
|
|
| |
Changed the tests so that the *.h5 test files are removed depending on the HDF5_NOCLEANUP environment variable.
bug 696
|
|
|
|
|
|
|
|
| |
H5Fget_obj_count to ssize_t and modified
C++ and Fortran API functions. This is for bug #1245.
Tested on smirom, linew, and kagiso.
|
|
|
|
| |
Fix for test of H5Tget_native_type_f
|
|
|
|
| |
Added test for h5tget_native_type_f
|
|
|
|
| |
Added the optional 'mounted' variable to H5Gget_info_by_idx_f/H5Gget_info_f/H5Gget_info_by_name_f to see that it passes the correct values.
|
|
|
|
| |
Added additional tests for h5sget_select_bounds_f
|
|
|
|
|
| |
Added additional tests for h5sget_select_hyper_blocklist_f
and 5sget_select_elem_pointlist_f
|
|
|
|
| |
Added test routines for h5t_get/set_fields_f.
|
|
|
|
| |
Fix the error of passing an array to a scalar.
|
|
|
|
|
|
|
|
| |
Initialized a string with a space instead of a blank
i.e. var = '' is now var = ' '
This fixes a problem with AIX for bug 1252
|
|
|
|
|
|
|
| |
Changed the INTENT for total_error to be consistantly
INTENT(INOUT)
as noted in bug 1251
|
|
|
|
|
|
| |
Changed the error output formatting so that the
test status writes to standard out looks correct when using the
sun compiler (it did not correctly tab the output).
|
| |
|
|
|
|
|
|
|
|
| |
Uninstall target had non-existant file to remove; error_handler module triggered
a race condition for parallel make with Intel and PGI compilers, therefore we
removed the module and created a subroutine instead.
Platforms tested: kagiso with GNU, Intel and PGI compilers.
|
|
|
|
| |
fixed typo (minor fix)
|
|
|
|
|
|
|
|
| |
Added code to remove module files when make clean
Description:
The module files were not being removed when make clean
and caused compiling errors. fixed.
|
|
|
|
|
|
|
| |
broken dependencies when
srcdir and parallel make are used; fixed (I hope)
Platforms tested: kagiso with srcdir and parallel make; pgcc and pgf90 -i8 compilers
|
|
|
|
|
|
| |
Broke-up longer lines over multiple lines
Removed unused variables.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Made reporting of the test status global by handling the output
via a module. Cleaned-up output to the terminal.
Description:
Put writing the test status as a call to a subroutine
instead of on a per account basis.
Added the dependency of compiling in the correct order
in the Makefiles for use of the Module.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
The fortran Makefile.am used HDF_FORTRAN to indicate it is part of the
Fortran API source so that conclude.am will give fortran api prefix in the
test output. The symbox HDF_FORTRAN is also used in configure for a different
purpose (indicated --enable-fortran). They conflicted.
Similar problem for the symbol HDF_CXX.
Solution:
Changed all the involved Makefile.am to use "FORTRAN_API" instead. It is
a more appropriate name. Same for CXX_API.
Along the way, discovered that the Makefile.am of hl/fortran/test and
hl/cxx/test did not have those symbols at all. Added them in.
Platform tested:
Kagiso only. It is a trivia change.
|
|
|
|
|
|
|
| |
Cleaned up unused code (i.e. commented out) and removed extraneous output to standard out.
Tested:
N/A - No critical executable source lines were modified, only comments and write statements.
|
|
|
|
|
|
|
| |
Description: cleaning up configure related to removal of --disable-hsizet
flag, which we no longer support.
Tested: kagiso
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Improvement.
Description:
src/libhdf5.settings was the initial configure summary and is installed.
Then configure is changed to dump a summary of the configure settings to
the output and also append it to src/libhdf5.settings. That created
two different output formats and duplicated information. This is the
initial attempt to clean up this confusion and unify the output format.
It is decided to use the src/libhdf5.settings template as the unified means.
This requires more macros symbols be defined. The following symbols are
all related to generating the src/libhdf5.settings file.
AC_SUBST(EXTERNAL_FILTERS)
AC_SUBST(MPE) MPE=no
AC_SUBST(STATIC_EXEC) STATIC_EXEC=no
AC_SUBST(HDF_FORTRAN) HDF_FORTRAN=no
AC_SUBST(FC) HDF_FORTRAN=no
AC_SUBST(HDF_CXX) HDF_CXX=no
AC_SUBST(CXX) HDF_CXX=no
AC_SUBST(HDF5_HL) HDF5_HL=yes
AC_SUBST(GPFS) GPFS=no
AC_SUBST(LINUX_LFS) LINUX_LFS=no
AC_SUBST(INSTRUMENT) INSTRUMENT=no
AC_SUBST(CODESTACK) CODESTACK=no
AC_SUBST(HAVE_DMALLOC) HAVE_DMALLOC=no
AC_SUBST(DIRECT_VFD) DIRECT_VFD=no
AC_SUBST(THREADSAFE) THREADSAFE=no
AC_SUBST(STATIC_SHARED)
AC_SUBST(enable_shared)
AC_SUBST(enable_static)
AC_SUBST(UNAME_INFO) UNAME_INFO=`uname -a`
The src/libhdf5.settings.in has CONDITIONAL's added to it too. The
untrue conditions turned into a "#" and these lines are cleaned by the
post processing script.
Platform tested:
h5committest on kagiso, smirom and linew.
|
|
|
|
| |
Cleaned up get_name_by_idx_f test that uses the newest API.
|
|
|
|
| |
Updated the call using the new interface for the get_name_by_idx_f routine
|
|
|
|
|
|
|
|
| |
manual testing using -i8 flag
Platforms tested: linew (as for daily tests), icc and pgf90 with -i8 on kagiso; g95 has the problem
with -i8 (will be looking into the problem)
|
|
|
|
|
|
|
|
| |
Fixed the validation problem with H5Aget_info_f
Desciption:
Recast the interger type passed into 'validate' subroutine.
|
|
|
|
| |
Added additional verification test for H5Aget_info_f
|
|
|
|
|
|
|
|
| |
Description:
There were a number of small tweaks we needed to make to add the new fortran_1_8 code on Windows. We create new project files, add new source to them, add the test to our test suite, and fix a few typos in the Windows-specific source code.
Tested:
VS2005 on WinXP
|
|
|
|
| |
Corrected the way the total number of errors are summed up.
|
|
|
|
| |
Added a test for H5Tget_create_plist_f
|
|
|
|
| |
test program.
|
|
|
|
| |
test program.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* test passing integer constant to subroutine
Description:
! -- CHECK PASSING AN INTEGER CONSTANT IN DIFFERENT FORMS --
! 1) call by passing an integer with the _hsize_t declaration
! 2) call by passing an integer with the INT(,hsize_t) declaration
! 3) call by passing a variable with the attribute hsize_t
|
| |
|
|
|
|
|
|
|
|
| |
test and source codes.
This check-in should address Fortran failures on liberty and smirom.
Platforms tested: kagiso with Intel, smirom with g95 -fPIC, liberty with gfortran42
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description: Applying update to autotools that was applied to 1.8 a couple
of weeks ago to the trunk.
Updated bin/reconfigure script to reflect the new versions of
libtool and automake in the /home1/packages/ directory.
Rearranged configure.in script. When using libtool 2.2.2, the
libtool script doesn't generate until later in the configuration
process, so I had to move a test that parsed through the libtool
script to a point after where it was actually being generated.
Ran libtoolize on the project, and ran bin/reconfigure to
regenerate configure and Makefile.in's throughout.
Tested: kagiso, smirom, linew (h5committest)
|
|
|
|
|
|
|
|
|
|
| |
failing previously on linew.
Currently only one test (dense attributes) is failing. It looks like C library problem and we
have a similar bug report in Bugzilla: when dense storage is used, attributes are not written
to the file; somehow similar C test doesn't expose the problem while Fortran test does.
Platforms tested: linew, kagiso with g95 and PGI
|
|
|
|
|
|
|
|
| |
with the g95 compiler
Platforms tested: kagiso with PGI compilers, linew, smirom with GCC and g95 compilers;
some tests and function calls are commented out with !EP string; we will be
working on it.
|
|
|
|
| |
tests are commented with !!EP for now.
|
|
|
|
| |
another test for linew before daily tests start.
|