| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
standard 2.8.6
|
|
|
|
|
|
| |
Added test for h5dget_space_status_f.
Tested: jam (gnu, intel, pgi)
|
|
|
|
|
|
|
| |
Changed, INTENT of flag to be OUT instead of IN for h5dget_space_status_f, the value gets changed so it should have intent(OUT), it
is correct in the documentation.
Tested: jam (gnu, intel, pgi)
|
| |
|
| |
|
|
|
|
| |
fortran/src and hl/fortran/src and the install command.
|
| |
|
| |
|
|
|
|
|
|
| |
Renamed hdf file dsetf.h5 to dsetf_F03.h5 to avoid a possible conflict with the same file created in the fortranlib_test.f90 test.
Tested: jam (pgi)
|
|
|
|
|
|
| |
Removed using INT() on an already INTEGER variable on the input argument to the verify routine, which was causing wrong verify results for the two integers on a Mac.
Tested: fred (gnu) in production mode.
|
| |
|
|
|
|
|
|
|
|
| |
files updated to link with fortran mpi libs.
Updated cacheinit.cmake to set num of procs to 3 for hdf testing.
Tested: local linux and on windows 7
|
| |
|
|
|
|
|
|
|
| |
in fortranlib_test.f90. I think it was causing the
make check -j8 race condition failures in daily tests.
Tested jam (gfortran, intel)
|
|
|
|
|
|
|
|
|
|
|
| |
> make failed:
> "../../../hdf5/fortran/test/fortranlib_test_1_8.f90", line 642.15:
> 1513-041 (S) Arguments of the wrong type were specified for the
> INTRINSIC procedure "mod".
Fixed by defining both arguments in MOD as integer size_t
Tested: jam (gfortran, intel)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*Hostname: nsipada0X:
"../../../hdf5/fortran/src/H5Ef.c", line 301.40: 1506-280 (E)
Function argument
assignment between types "int(*)(int,void*)" and "int(*)(int,struct
{...}*)" is
not allowed.
Fixed by casting has H5E_auto2_t.
tested: jam (gfortran, intel)
|
|
|
|
|
|
| |
OPTION command for solution folder and no packaging.
Tested: local linux
|
|
|
|
|
|
| |
Fixed the GM offset returned in the derived type h5_info_t and use the functon HDgmtime instead of gmtime.
tested: jam( intel, gnu)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removed line:
$(RM) $(DESTDIR)$(includedir)/H5f90i*.h
These *.h files are needed for HL_NPOESS and should not be removed when make clean is specified.
The Daily Test installs the file using the deploy script, but then
runs make clean which removes the file, so the files are not there when we try to compile HL_NPOESS
causing an error.
|
|
|
|
|
|
|
|
| |
Changed the API to pass type(h5o_info_t) instead of a C pointer to the derived type.
Tested:
jam (gfortran and pgi)
|
| |
|
| |
|
|
|
|
|
|
| |
the hdf5 library.
tested: jam (intel)
|
| |
|
|
|
|
| |
RM, no source changes.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
H5close are needed in the corresponding
Fortran wrappers.
Solutions: The calls were not needed and were removed from the C stubs h5open_c and h5close_c for the correspnding
Fortran subroutines h5open_f and h5close_f.
Platforms tested: jam with gcc and gfortran, PGI and Intel
koala with PGI and Intel
linew with the standard Sun compilers
|
|
|
|
|
|
| |
Modified h5oget_info_by_name_f to return a derive type h5o_info_t
Tested: jam( gfortran, pgi, intel)
|
|
|
|
|
|
|
|
| |
F2003_new branch for
further testing.
Tested: jam (gnu)
|
|
|
|
|
|
|
| |
Updated to the robodoc headers comments, cleaned up the spacing of the
source code which is included in the documenaton.
Tested: jam (intel)
|
| |
|
|
|
|
|
|
| |
multi-dimensional arrays detected using xlf compiler.
Tested: jam (intel, gnu, pgi) F2003 compilers.
|
| |
|
| |
|
|
|
|
|
|
| |
fortran types, it was not used in the main fortran src.
Tested: jam (gnu, g95, intel)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
H5_ff_F90/F03.lo and H5_ff.lo
to resolve failures when building HDF5.lo and HDF5mpio.lo.
Tested: jam (gcc, mpi) using both: make HDF5.lo and make HDF5mpio.lo
|
| |
|
|
|
|
| |
to the RM documentation's standards.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
type to c_long to match the unsigned long, via standard:
F2003, Note 15.9
"The C international standard specifies that the representations for
nonnegative signed integers ar ethe same as the corresponding
values for signed integers. Because Fortran does not provide direct
support for unsigned kinds of integers, the ISO_C_BINDING module
does not make accessible named constants for their kind type
parameter values. Instead, a user can use the signed kinds of
integers to interoperate with the unsigned types and all their
qualified versions as well...."
Tested: (jam, intel)
|
| |
|
|
|
|
|
|
|
| |
fortran (using F2003), for both 1D and 2D array of vl strings.
Tested: jam (pgi, gfortran 4.5, ifort)
linew (12.3 beta)
|
| |
|
|
|
|
|
|
| |
changed the INTEGER type getting passed the verify* programs in the test programs. Fixes problems with Sun compilers 12.3 beta with the -m64 flag.
Tested: linew( 12.3 beta)
|