| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
H5_HAVE_C99_DESIGNATED_INITIALIZER and H5_HAVE_C99_FUNC.
I tested them for v1.8. I simply added them by hand for v1.9 for now. I'll test them later.
|
|
|
|
|
|
|
| |
Moved a comment up to a more appropriate spot.
No execution change.
Tested: jam pp.
|
| |
|
|
|
|
|
| |
The test "h5diff -v h5diff_hyper1.h5 h5diff_hyper2.h5" sometimes hangs in THG
machines. Skip it until its hanging is resolved.
|
|
|
|
| |
for 1.8.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code Cleanup
Description:
- Pulled out repetitive cache stats code into its own new macro.
- Converted HDasserts in cache stats macros to if / HGOTO_ERROR statments
in order to keep code consistent.
Tested:
jam, smirom, liberty
|
|
|
|
|
|
|
|
|
|
|
| |
Improvement
Description:
Modified the warning messages from the Version mismatch checking to suggest
the users to try recompiling or checking the shared lib setting.
Platforms tested:
Tested in Jam only since it was just a simple text string changes.
|
|
|
|
| |
tested: windows, linux
|
|
|
|
| |
Tested on jam. Tested v1.8 on OpenVMS.
|
|
|
|
|
|
|
|
|
| |
Description:
If a compound type was packed except for some extra space at the end, H5Tpack
would not modify the type and the extra space would remain. Changed
H5T_is_packed to fix this behaviour.
Tested: jam, smirom (h5committest - linew down)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bring r16305 back from revise_chunks branch:
Add detection of C99 "designated initializers" to configure script and
use new H5_HAVE_C99_DESIGNATED_INITIALIZER macro to conditionally compile
default layout variables in src/H5Pdcpl.c
Also, minor code cleanups, etc.
Tested on:
FreeBSD/32 6.3 (duty) in debug mode
(Other platforms tested on branch)
|
|
|
|
|
|
|
|
|
| |
added:
!DEC$ATTRIBUTES reference ::
for character strings being passed in to C to fix bug in VMS for functions
h5sdecode_f and h5sencode_f.
|
|
|
|
|
|
|
|
|
|
| |
compression is 1024 bytes
M - is an integer greater than 1, size of dataset in bytes (default is 1024)
#bgz 1426
tested: windows, linux
|
|
|
|
|
|
|
| |
-N, --nan Avoid NaNs detection
Note: there is no shell script run for datasets with NaN because the output is non portable (different results and NaN strings for different systems)
Tested: windows, linux
|
|
|
|
|
|
|
|
|
| |
Storage: information not available
When displaying storage information for VL and dataset region types
Added 2 shell runs that display this information
#818
Tested: windows, linux
|
|
|
|
|
|
| |
Disable more file drivers incompatible with family file driver in external_set_elink_cb in links.c.
Tested: jam check-vfd
|
|
|
|
|
|
|
|
| |
used as the member
file driver for a family file. This was causing problems with check-vfd.
Tested: jam
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Descriotion:
Removing problematic debugging code, and switching a leftover TRUE verbose
statement to FALSE in cache_common.c
Tested:
jam, liberty
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adding code to maintain a min_clean_fraction in the cache in serial mode.
Description:
The metadata cache now has the ability to maintain a min_clean_fraction
when in serial mode. The default initial cache size has been changed
from 1MB to 2MB, and the default min_clean_fraction has been set at 30%.
This check-in includes modifications to H5C.c to support maintaining a
min_clean_size, including the addition of clean_index_size and
dirty_index_size trackers, modifications to the H5C_make_space_in_cache
algorithm, as well as associated test code and additional statistics
tracking variables.
Maintaining the min_clean_fraction addresses the possibility of
experiencing a "metadata blizzard" when the cache gets completely
full with dirty entries. Upon having to make space, the cache would
previously need to flush every single entry in the cache before coming
across a clean entry which could be evicted. This resulted in unnecessary
flushing of oftentimes hot entries in the cache. Maintaining the
min_clean_fraction ensures that, when space is needed, clean entries
are more readily available to evict.
Tested:
jam, smirom, linew (h5committest)
|
|
|
|
| |
Tested: jam
|
|
|
|
|
|
|
|
| |
longer copies the
driver information from property list to property list.
Tested: jam
|
|
|
|
|
|
|
|
|
|
|
| |
- h5repack: When user doesn't specify a chunk size, h5repack now defines a default
chunk size as the same size of the size of the hyperslab used to read the chunks.
The size of the hyperslabs are defined as the size of each dimension or a
predefined constant, whatever is smaller. This assures that the chunk
read fits in the chunk cache. (PVN - 2008/11/21)
- H5Dset_extent: when shrinking dimensions, some chunks were not deleted.
(PVN - 2009/01/8)
|
|
|
|
|
|
|
|
|
|
|
| |
external links.
Description: Added H5Pset/get_elink_cb to allow the user to specify a callback
function to be called whenever an external link is traversed. Added
H5Pset/get_elink_acc_flags to allow the user to specify the file access flags
to use to open the target file of an external link. All these properties are set on a LAPL.
Tested: jam, linew, smirom (h5committest)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bring revision 16278 back from revise_chunks branch:
Update layout information in DCPL to unify all information in one
underlying property and switch to using H5O_layout_t for storing it, which
simplifies things considerably.
Also, fix many compiler warnings.
Tested on:
FreeBSD/32 6.3 (duty) in debug mode
(Original patch tested on many machines)
|
|
|
|
| |
Tested: windows, linux
|
|
|
|
|
|
|
|
|
| |
The Tail command in jam (a newer linux) does not accept the +2l option.
It ended up wiping most of the release_doc/RELEASE.txt file contents.
Replaced the "tail +2l" by "sed -e 1d".
Tested:
Tested in Jam to verify it functions properly again.
|
|
|
|
|
|
|
|
| |
by hdftest.
Update version number listed at the top.
Tested: vim
|
|
|
|
|
|
|
|
| |
added missing reference in h5lget_name_by_idx_f:
!DEC$ATTRIBUTES reference ::
for character strings being passed in to C to fix bug in VMS.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
cleaned more linux warnings
tested: linux
|
|
|
|
| |
tested: linux
|
|
|
|
| |
tested: windows, linux
|
|
|
|
|
|
|
|
| |
datasets and contiguous with no external storage
new test program: It adds tests for several ranks, use of fill value or not, compression, different fill value allocation times, use of different storage layouts, and external files
tested: windows, linux
|
| |
|
|
|
|
|
|
|
| |
PG compiler complains about array out of bounds (a rank of zero was not checked)
Adding a scalar dataset to the test generator program. this case is run on a previous existing run, the case was added to 2 existing files
Tested: windows, linux
|
|
|
|
|
|
|
|
|
| |
to rewind the file pointer
to the beginning of the file. Otherwise, the file might be re-extended later on Open VMS.
Also updated the return value for the HDlseek to be more appropriate.
Tested 1.8 on Open VMS.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix (#1357)
Description:
Three filters have not assigned correct value to one value-result argument, "buf_size". N-bit, szip, and scale offset filter have had this problem.
However, I don't think this problem has been making buffer overrun because those filters were informing the caller that the "buf", another value-result argument, is smaller than it actually is. If there was actual buffer overrun, I believe another problem exists although I don't know.
Tested:
jam, smirom, linew
Although all test were passed, I'm concerned about valgrind memcheck error. There can be another miscommunication between filter and the caller.
|
|
|
|
| |
using VS2008 Express.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Moved v1 B-tree debugging routines into separate module and thinned
out header files a bit.
Tested on:
Mac OS X/32 10.5.5 (amazon) in debug mode
Mac OS X/32 10.5.5 (amazon) w/C++ & FORTRAN, w/threadsafe,
in production mode
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
|
|
|
|
|
|
|
|
|
| |
H5FD_sec2_truncate for VMS only.
On Open VMS, if the last read or write put the file pointer beyond the current file size
(it happens when an object is deleted), the file can be extended when it's truncated.
Tested v1.8 on VMS.
|
|
|
|
|
|
|
|
| |
added:
!DEC$ATTRIBUTES reference ::
for character strings being passed in to C to fix bug in VMS.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
Resolved issues with broken sanity checks that were failing when the 'b2'
debugging package was enabled (v2 b-tree debugging):
- Fixed outdated assertions that would not compile. They now compile
and function correctly.
- Removed too far outdated assertions that would require too much
unnecessary refactoring of code in order to satisfy their
initial purpose.
- Re-enabled b2 debugging package when "--enable-debug=all" is
specified on the configure line.
Tested:
jam, smirom, linew
|
|
|
|
| |
(Related to revision 16180)
|
|
|
|
|
|
|
| |
Change a few more "istore" references in comments to "chunk" or "btree".
Tested on:
None, just comments
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename internal routines, variables, macros, typedefs, etc. for chunked
dataset storage from "istore" to some variant of "chunk" or "btree".
Tested on:
Mac OS X/32 10.5.5 (amazon) in debug mode
Mac OS X/32 10.5.5 (amazon) w/C++ & FORTRAN, w/threadsafe,
in production mode
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
|
|
|
|
|
|
|
|
|
|
| |
Rename the current chunk indexing routines module for B-tree indices
to better reflect their purpose, and to make the upcoming extensible array
index module fit in better.
Tested:
FreeBSD/32 6.3
Too minor to require h5committest
|
|
|
|
|
|
|
|
| |
Use the H5F_KVALUE macro in a couple more places, to make the code
easier to read.
Tested on:
Mac OS X only (very minor)
|
|
|
|
| |
Tested: jam
|
| |
|