- updated to 1.8.3:
    - Added an H5free_memory API call. This should be used to free memory 
      that has been allocated by HDF5 API calls. H5Tget_member_name and 
      H5Pget_class_name are two examples. The main motivation for this call 
      is Windows, where it is common for application code and the HDF5 Library 
      to be using different C run-time libraries (CRT). Using the new call 
      ensures that the same CRT handles both the allocation and free. This 
      new function can also be useful in any case where the library uses a 
      different memory manager than the application, such as when a debug 
      memory manager is in use or when the HDF5 Library is wrapped for use 
      in a managed language like Python or Java. Fixes HDFFV-7710, 8519, 
      and 8851. (DER - 2014/04/11)
    - The Core VFD (aka Memory VFD) can now be configured to track dirty 
      regions in the file and only write out the changed regions on 
      flush/close. Additionally, a "page aggregation" size can be set that 
      will aggregate small writes into larger writes. For example, setting 
      a 1 MiB page aggregation size will logically partition the the 
      in-memory file into 1 MiB pages that will be written out in their 
      entirety if even a single byte is dirtied. The feature is controlled 
      via the new H5Pset/get_core_write_tracking() API call. A new 
      "core_paged" target has been added to the check-vfd target in 
      test/Makefile.am that exercises the feature over all HDF5 VFD-aware
      tests. (DER - 2014/04/12)
    - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
      for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch

• Files Changed
• Browse Source