summaryrefslogtreecommitdiffstats
path: root/Demo/threads
diff options
context:
space:
mode:
Diffstat (limited to 'Demo/threads')
0 files changed, 0 insertions, 0 deletions
generated by cgit v0.12 at 2026-02-13 16:08:33 (GMT)
e/hdf5_rados'>inactive/hdf5_rados Mirror from: https://github.com/HDFGroup/hdf5.git
summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r16620] commented a run that fails cross platforms (liberty, abe) ↵Pedro Vicente Nunes2009-03-261-1/+1
| | | | regarding a "double" print
* [svn-r16618] Description:Quincey Koziol2009-03-265-145/+363
| | | | | | | | | | | | | | | | | | | | | | Modify metadata cache flush dependency feature to allow it to work with entries that are pinned through the cache API calls. Tested on: FreeBSD/32 6.3 (duty) in debug mode FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode Linux/32 2.6 (jam) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe, in debug mode Linux/64-amd64 2.6 (smirom) w/Intel compilers w/default API=1.6.x, w/C++ & FORTRAN, in production mode Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN, w/szip filter, in production mode Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN, in production mode Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode Linux/64-amd64 2.6 (abe) w/parallel, w/FORTRAN, in production mode Mac OS X/32 10.5.6 (amazon) in debug mode Mac OS X/32 10.5.6 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode
* [svn-r16617] Update RELEASE.txt with changes committed in revision 16615. ↵Neil Fortner2009-03-261-5/+9
| | | | | | | | Also add some bug numbers to entries in RELEASE.txt. Tested: kate
* [svn-r16615] Purpose: Fix bug 1499Neil Fortner2009-03-263-4/+140
| | | | | | | | | | | Description: Due to a bug in H5F_super_read, every time a file with a user block was opened it would grow by the size of the user block. The bug has been fixed, and comments have been added to clarify when an eoa address should be relative and when it should be absolute. Tested: jam, linew (h5committest)
* [svn-r16614] 3. #1501 (B1) tools bug if dataset is larger than ↵Pedro Vicente Nunes2009-03-2516-21/+191
| | | | | | | | | | | | H5TOOLS_BUFSIZE limit. ISSUE : the tools use the following formula to read by hyperslabs: hyperslab_size[i] = MIN( dim_size[i], H5TOOLS_BUFSIZE / datum_size) where H5TOOLS_BUFSIZE is a constant defined of 1024K. This is OK as long as the datum_size does not exceed 1024K, otherwise we have a hyperslab size of 0 (since 1024K/(greater than 1024K) = 0). This affects h5dump. h5repack, h5diff SOLUTION: add a check for a 0 size and define as 1 if so. TEST FOR H5DUMP: Defined a case in the h5dump test generator program of such a type (an array type of doubles with a large array dimension, that was the case the user reported). Since the written file commited in svn would be around 1024K, opted for not writing the data (the part of the code where the hyperslab is defined is executed, since h5dump always reads the files). Defined a macro WRITE_ARRAY to enable such writing if needed. Added a run on the h5dump shell script. Added 2 new files to svn: tools/testfiles/tarray8.ddl, tools/testfiles/tarray8.h5. NOTE: while doing this I thought of adding this dataset case to an existing file, but that would add the large array output to those files (the ddls). The issue is that the file list is increasing. TEST FOR H5DIFF: for h5diff the check for reading by hyperslabs is H5TOOLS_MALLOCSIZE (128 * H5TOOLS_BUFSIZE) or 128 Mb. This makes it not possible to add such a file to svn, so used the same method as h5dump (only write the dataset if WRITE_ARRAY is defined). As opposed to h5dump, the hyperslab code is NOT executed when the dataset is empty (dataset is not read). Added the new dataset to existing files and shell run (tools/h5diff/testfiles/h5diff_dset1.h5 and tools/h5diff/testfiles/h5diff_dset2.h5 and output in tools/h5diff/testfiles/h5diff_80.txt). TEST FOR H5REPACK: similar issue as h5diff with the difference that the hyperslab code is run. Added a run to the shell script (with a filter, otherwise the code uses H5Ocopy). tested: linux (h5commitest failed , apparently it did not detect the code changes in /tools/lib that fix the bug: the error in an assertion in the hyperslab of 0. I am sure that making h5ccomitest --distclean will detect the new code , but don't want to wait more 3 hours :-) )
* [svn-r16612] I changed the API function H5Dopen to H5Dopen2, which I ↵Raymond Lu2009-03-251-2/+2
| | | | | | introduced in recent checkin. Tested on jam - simple change.
* [svn-r16611] In previous checkin (r16609), the flag "write_driver" wasn't ↵Raymond Lu2009-03-253-13/+9
| | | | | | | | necessary as Quincey pointed out. I took it out and used the driver address instead. Tested on jam - simple change.
* [svn-r16609] Bug fix (#1161): When a family file created with v1.6 library ↵Raymond Lu2009-03-247-7/+50
| | | | | | | | | | | is opened and closed with v1.8 library, v1.8 library writes the driver info block in the superblock. But v1.6 doesn't write it. This caused the data after the superblock to be overwritten. The solution is to use a flag to indicate when the original file doesn't have the driver info, v1.8 library doesn't write it either. Tested on jam. I have some trouble to access smirom and linew using h5committest.
* [svn-r16606] Description:Quincey Koziol2009-03-242-0/+109
| | | | | | | | | Add H5AC_create_flush_dependency() and H5AC_destroy_flush_dependency() wrappers for similarly named routines in H5C layer. Tested on: FreeBSD/32 6.3 (duty) Too minor to require h5committest
* [svn-r16600] Description:Quincey Koziol2009-03-245-1434/+3571
| | | | | | | | | | | | | | | | | | Ensure that metadata cache entries with flush dependencies are written to the file in the correct order (for serial I/O, at least). Tested on: FreeBSD/32 6.3 (duty) in debug mode FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode Linux/32 2.6 (jam) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe, in debug mode Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN, in production mode Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode Linux/64-amd64 2.6 (abe) w/parallel, w/FORTRAN, in production mode Mac OS X/32 10.5.6 (amazon) in debug mode Mac OS X/32 10.5.6 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode
* [svn-r16599] added the notePedro Vicente Nunes2009-03-231-0/+6
| | | | | | | Fortran High-Level APIs: ------ - Lite: The h5ltget_dataset_info_f function (gets information about a dataset) was not correctly returning the dimension array (PVN - 2009/3/23)
* [svn-r16597] #1047 (B1) The h5lt info routines are returning data in ↵Pedro Vicente Nunes2009-03-232-21/+86
| | | | | | transposed form. ISSUE : the dimension array of the function h5ltget_dataset_info_f was not transposed (because of C-FORTRAN storage order, the FORTRAN function calls the C function with the same name). SOLUTION: transpose the array. ACTION: add a test case. tested: h5committest
* [svn-r16596] Update RELEASE.txt with changes committed in revision 16594.Neil Fortner2009-03-231-0/+6
| | | | Tested: kate
* [svn-r16594] Purpose: fix bug 1189Neil Fortner2009-03-23