mirror/hdf5
2
0
Fork 0
mirror of https://github.com/HDFGroup/hdf5.git synced 2025-02-05 15:42:32 +08:00
Code Issues Packages Projects Releases Wiki Activity
10,997 Commits 88 Branches 143 Tags 619 MiB
C 80%
Fortran 4.4%
Java 3.9%
CMake 3.2%
C++ 2.4%
Other 6%
92b11988c8
Go to file
Quincey Koziol 92b11988c8 [svn-r16532] Description: 
Pass the chunk "user data" to H5D_chunk_unlock(), so that chunks with
an address already aren't reallocated.

Tested on:
        FreeBSD/32 6.3 (duty) in debug mode
        FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode
        Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
2009-03-02 15:57:18 -05:00
bin [svn-r16340] Description: 2009-01-22 15:53:59 -05:00
c++ [svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a 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) 2009-02-26 15:21:50 -05:00
config [svn-r16525] Snapshot version 1.9 release 33 2009-03-01 09:35:48 -05:00
examples [svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a 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) 2009-02-26 15:21:50 -05:00
fortran [svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a 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) 2009-02-26 15:21:50 -05:00
hl [svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a 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) 2009-02-26 15:21:50 -05:00
perform [svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a 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) 2009-02-26 15:21:50 -05:00
release_docs [svn-r16525] Snapshot version 1.9 release 33 2009-03-01 09:35:48 -05:00
src [svn-r16532] Description: 2009-03-02 15:57:18 -05:00
test [svn-r16523] Purpose: Fix bugs related to H5Dset_extent and fill values 2009-02-27 12:01:00 -05:00
testpar [svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a 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) 2009-02-26 15:21:50 -05:00
tools [svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a 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) 2009-02-26 15:21:50 -05:00
vms [svn-r16525] Snapshot version 1.9 release 33 2009-03-01 09:35:48 -05:00
windows [svn-r16525] Snapshot version 1.9 release 33 2009-03-01 09:35:48 -05:00
windows_vnet [svn-r16412] testh5ls.bat - added tests to match script file from rev 16310 2009-02-03 16:38:14 -05:00
.autom4te.cfg [svn-r13314] Updated copyright notice. 2007-02-14 17:55:20 -05:00
.h5chkright.ini [svn-r13314] Updated copyright notice. 2007-02-14 17:55:20 -05:00
aclocal.m4 [svn-r15942] Purpose: Bug Fixes and Libtool Upgrade 2008-10-24 12:19:34 -05:00
acsite.m4 [svn-r12183] Purpose: 2006-03-30 18:08:50 -05:00
configure [svn-r16525] Snapshot version 1.9 release 33 2009-03-01 09:35:48 -05:00
configure.in [svn-r16525] Snapshot version 1.9 release 33 2009-03-01 09:35:48 -05:00
COPYING [svn-r16409] Description: 2009-02-03 14:36:58 -05:00
Makefile.am [svn-r15041] Purpose: Configure Fix 2008-05-19 16:12:16 -05:00
Makefile.dist [svn-r13311] Updated copyright notice. 2007-02-14 17:25:02 -05:00
Makefile.in [svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a 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) 2009-02-26 15:21:50 -05:00
MANIFEST [svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a 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) 2009-02-26 15:21:50 -05:00
README.txt [svn-r16525] Snapshot version 1.9 release 33 2009-03-01 09:35:48 -05:00

README.txt 

HDF5 version 1.9.34 currently under development
==> README.txt <==
Messages to be sent to the list should be sent to "<list>@hdfgroup.org".

Periodic code snapshots are provided at the following URL:
    ftp://ftp.hdfgroup.uiuc.edu/pub/outgoing/hdf5/snapshots
Please read the README.txt file in that directory before working with a library
snapshot.

The HDF5 website is located at http://hdfgroup.org/HDF5/

Bugs should be reported to help@hdfgroup.org.