1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
|
HDF5 History
============
This file contains development history of the HDF5 1.10 branch
02. Release Information for hdf5-1.10.0-patch1
01. Release Information for hdf5-1.10.0
[Search on the string '%%%%' for section breaks of each release.]
%%%%1.10.0-patch1%%%%
HDF5 version 1.10.0-patch1 released on 2016-05-23
================================================================================
INTRODUCTION
This document describes the differences between HDF5-1.8 series and
HDF5 1.10.0 releases, and contains information on the platforms
tested.
Links to HDF5 1.10.0 source code can be found on The HDF Group's
development FTP server at the following location:
https://www.hdfgroup.org/HDF5/release/obtain5110.html
User documentation can be accessed directly at this location:
https://www.hdfgroup.org/HDF5/docNewFeatures/
For more information, see the HDF5 home page:
https://www.hdfgroup.org/HDF5/
If you have any questions or comments, please send them to the HDF
Help Desk:
help@hdfgroup.org
CONTENTS
- New Features
- Issues Addressed in this Release
- Supported Platforms
- Tested Configuration Features Summary
- More Tested Platforms
- Known Problems and Limitations
New Features
============
This release supports the following features:
Configuration
-------------
- API Compatibility with HDF5 1.8 Flag Was Added
The 1.10 version of the HDF5 Library can be configured to operate
identically to the 1.8 library with the --with-default-api-version=v18
configure flag. This allows existing code to be compiled with the 1.10
library without requiring immediate changes to the application source
code. For addtional configuration options and other details, see
"API Compatibility Macros in HDF5" at
https://www.hdfgroup.org/HDF5/doc/RM/APICompatMacros.html.
- Autotools Configuration Has Been Extensively Reworked
The autotools configuration options have been updated to allow more
fine-grained control of the build options and to correct some bugs.
See configure --help for comprehensive information on each option.
Specific changes:
* --enable-debug and --enable-production are no longer accepted.
Use --enable-build-mode=(debug | production) instead. These set
appropriate defaults for symbols, optimizations, and other
configuration options. These defaults can be overridden by the
user.
* Extra debug output messages are no longer enabled with
--enable-debug=<package list>. Use --enable-internal-debug=<pkg list>
instead.
* A new --enable-symbols option allows symbols to be generated
independently of the build mode. --disable-symbols can be used
to strip symbols from the binary.
* A new --enable-asserts option sets/unsets NDEBUG. This is
independent of the build mode. This also enables some extra
low-overhead debug checks in the library.
* A new --enable-profiling option sets profiling flags. This is
independent of the build mode.
* A new --enable-optimization option sets the optimization level.
This is independent of the build mode.
* Many of these options can take a flags string that will be used
to build the library. This can be useful for specifying custom
optimization flags such as -Os and -Ofast.
* gnu C++ and Fortran use configure sub-files that update the
build flags and turn on warnings. The increase in warnings when
building these wrapper libraries is due to these flag changes
and not to a decrease in code quality.
* The option to clear file buffers has been removed. Any buffer that
will eventually be written to disk will now always be memset
to zero. This prevents the previous contents of the buffer from
being written to the disk if the buffer contents are not
completely overwritten, which has security implications.
- LFS Changes
The way the autotools handle large file support (LFS) has been
overhauled in this release.
* We assume ftello and fseeko exist
* We no longer explicitly use the *64 I/O functions. Instead, we
rely on a mapping provided by _FILE_OFFSET_BITS or its equivalent.
* _LARGEFILE(64)_SOURCE is no longer exported via AM_CPPFLAGS.
Parallel Library
-----------------
- Collective Metadata I/O
Calls for HDF5 metadata can result in many small reads and writes.
On metadata reads, collective metadata I/O can improve performance
by allowing the library to perform optimizations when reading the
metadata by having one rank read the data and broadcasting it to
all other ranks.
Collective metadata I/O improves metadata write performance through
the construction of an MPI derived datatype that is then written
collectively in a single call. For more information, see
https://www.hdfgroup.org/HDF5/docNewFeatures/NewFeaturesCollectiveMetadataIoDocs.html.
Library
--------
- Concurrent Access to HDF5 Files - Single Writer/ Multple Reader (SWMR)
The Single Writer/ Multiple Reader or SWMR feature enables users to
read data concurrently while writing it. Communications between the
processes and file locking are not required. The processes can run
on the same or on different platforms as long as they share a common
file system that is POSIX compliant. For more information, see the
Single-Writer/Multiple-Reader (SWMR) documentation at
https://www.hdfgroup.org/HDF5/docNewFeatures/NewFeaturesSwmrDocs.html.
- Virtual Dataset (VDS)
The VDS feature enables data to be accessed across HDF5 files
using standard HDF5 objects such as groups and datasets without
rewriting or rearranging the data. An HDF5 virtual dataset (VDS)
is an HDF5 dataset that is composed of source HDF5 datasets in
a predefined mapping. VDS can be used with the SWMR feature. For
documentation, check
https://www.hdfgroup.org/HDF5/docNewFeatures/NewFeaturesVirtualDatasetDocs.html.
- Persistent Free File Space Tracking
Usage patterns when working with an HDF5 file sometimes result in
wasted space within the file. This can also impair access times
when working with the resulting files. The new file space management
feature provides strategies for managing space in a file to improve
performance in both of these areas. For more information, see
https://www.hdfgroup.org/HDF5/docNewFeatures/NewFeaturesFileSpaceMgmtDocs.html.
- Version 3 Metadata Cache
The version 3 metadata cache moves management of metadata I/O from
the clients to the metadata cache proper. This change is essential for
SWMR and other features that have yet to be released.
C++ Library
------------
- New Member Function Added to H5::ArrayType
The assignment operator ArrayType::operator= was added because
ArrayType has pointer data members.
(BMR - 2016/03/07, HDFFV-9562)
Tools
------
- h5watch
The h5watch tool allows users to output new records appended to
a dataset under SWMR access as it grows. The functionality is
similar to the Unix user command "tail" with the follow option,
which outputs appended data as the file grows. For more
information, see
https://www.hdfgroup.org/HDF5/docNewFeatures/NewFeaturesSwmrDocs.html#Tools.
- h5format_convert
The h5format_convert tool allows users to convert the indexing
type of a chunked dataset made with a 1.10.x version of the HDF5
Library when the latest file format is used to the 1.8.x version 1 B-tree indexing
type. For example, datasets created using SWMR access, can be
converted to be accessed by the HDF5 1.18 library and tools. The
tool does not rewrite raw data, but it does rewrite HDF5 metadata.
High-Level APIs
----------------
- H5DOappend
The function appends data to a dataset along a specified dimension.
C Packet Table API
------------------
- Replacement of a Public Function with H5PTcreate
The existing function H5PTcreate_fl limits applications so they
can use the deflate compression only. The public function
H5PTcreate has been added to replace H5PTcreate_fl. H5PTcreate
takes a property list identifier to provide flexibility on
creation properties.
(BMR - 2016/03/04, HDFFV-8623)
- New Public Functions: H5PTget_dataset and H5PTget_type
Two accessor functions have been added. H5PTget_dataset returns
the identifier of the dataset associated with the packet table,
and H5PTget_type returns the identifier of the datatype used by
the packet table.
(BMR, 2016/03/04, HDFFV-8623)
- Regarding #ifdef VLPT_REMOVED
The #ifdef VLPT_REMOVED blocks have been removed from the packet
table (PT) library source except for the following functions:
+ H5PTis_varlen() has been made available again
+ H5PTfree_vlen_readbuff() is now H5PTfree_vlen_buff()
(BMR - 2016/03/04, HDFFV-442)
C++ Packet Table API
--------------------
- New Constructor Added to FL_PacketTable
An overloaded constructor has been added to FL_PacketTable and
takes a property list identifier to provide flexibility on
creation properties.
(BMR - 2016/03/08, HDFFV-8623)
- New Public Functions
Two accessor wrappers are added to class PacketTable.
PacketTable::GetDataset() returns the identifier of the dataset
associated with the packet table, and PacketTable::GetDatatype()
returns the identifier of the datatype that the packet table uses.
(BMR - 2016/03/04, HDFFV-8623)
- Member Functions with "char*" as an Argument
Overloaded functions were added to provide the "const char*"
argument; the existing version will be deprecated in future
releases.
(BMR - 2016/03/04, HDFFV-8623)
- Regarding #ifdef VLPT_REMOVED
The #ifdef VLPT_REMOVED blocks have been removed from the packet
table library source code except for the following functions:
+ VL_PacketTable::IsVariableLength() was moved to PacketTable
+ VL_PacketTable::FreeReadBuff() is now PacketTable::FreeBuff()
(BMR - 2016/03/04, HDFFV-442)
Java Wrapper Library
--------------------
The Java HDF5 JNI library has been integrated into the HDF5 repository.
The configure option is "--enable-java", and the CMake option is
HDF5_BUILD_JAVA:BOOL=ON. The package hierarchy has changed from the
HDF5 1.8 JNI, which was "ncsa.hdf.hdflib.hdf5", to HDF5 1.10,
"hdf.hdflib.hdf5".
A number of new APIs were added including some for VDS and SWMR.
Other Important Changes
-----------------------
The hid_t type was changed from 32-bit to a 64-bit value.
Issues Addressed in this Release Since 1.10.0
=============================================
- h5diff would return from a compare attributes abnormally if one of the datatypes
was a vlen. This resulted in a memory leak as well as an incorrect report of
attribute comparison.
Fixed.
(ADB - 2016/04/26, HDFFV-9784)
- The JUnit-interface test may fail on Solaris platforms. The result of
a test for verifying the content of the error stack to stdout is
in a different order on Solaris then other platforms.
This test is skipped on Solaris
(ADB - 2016/04/21, HDFFV-9734)
- When building HDF5 with Java using CMake and specifying Debug for CMAKE_BUILD_TYPE,
there was a missing command argument for the tests of the examples.
Fixed.
(ADB - 2016/04/21, HDFFV-9743)
- Changed h5diff to print a warning when a dataset is virtual, enabling
the data to be compared. In addition h5repack failed to copy the data
of a virtual dataset to the new file. Function H5D__get_space_status changed
to correctly determine the H5D_space_status_t allocation value.
CMake added the Fixed Array indexing tests that were only in the autotools
test scripts.
Fixed and tests added for vds issues.
(ADB,NAF - 2016/04/21, HDFFV-9756)
- CMake added the h5format_convert tool and tests that were only in the autotools
build and test scripts. The autotools test script was reworked to allow CMake
to execute the test suite in parallel.
Also, h5clear tool and tests were added to the misc folder.
Fixed.
(ADB - 2016/04/21, HDFFV-9766)
- CMake added the h5watch tool and argument tests that were only in the autotools
build and test scripts. The POSIX only tests were not added to CMake.
CMake HL tools files were refactored to move the CMake test scripts into each tool folder.
Fixed.
(ADB - 2016/04/21, HDFFV-9770)
- Configure fails to detect valid real KINDs on FreeBSD 9.3 (i386) with Fortran enabled.
Fixed. Added the exponential option to SELECTED_REAL_KIND to distinguish
KINDs of same precision
(MSB - 2016/05/14,HDFFV-9912)
- Corrected the f90 H5AWRITE_F integer interface's buf to be INTENT(IN).
(MSB - 2016/05/14)
- Configure fails in sed command on FreeBSD 9.3 (i386) with Fortran enabled.
Fixed.
(MSB - 2016/05/14,HDFFV-9912)
- Compile time error in H5f90global.F90 with IBM XL Fortran 14.1.0.13 on BG/Q with Fortran
enabled.
Fixed.
(MSB - 2016/05/16,HDFFV-9917)
- A cmake build with Fortran enabled does not install module h5fortkit
Fixed.
(MSB - 2016/05/23,HDFFV-9923)
Issues Addressed in this Release Since alpha1
=============================================
- H5Pget_virtual_printf_gap, H5Pget_virtual_view, H5Pget_efile_prefix
The correct access property list settings from the
H5Pget_virtual_printf_gap, H5Pget_virtual_view, and
H5Pget_efile_prefix function calls could not be retrieved
using H5Dget_access_plist().
Fixed.
(DER and NAF - 2016/03/14, HDFFV-9716)
- h5dump
When h5dump was provided with the name of a non-existing file or
when optional arguments were the last option on the command line,
h5dump would segfault.
Fixed.
(ADB 2016/02/28 HDFFV-9639, HDFFV-9684)
- No Error Message for Corrupt Metadata
The HDF5 Library did not propagate an error when it encountered
corrupt metadata in an HDF5 file. The issue was fixed for a
specific file provided by a user. If you still see the problem,
please contact help@hdfgroup.org
Fixed.
(MC - 2016/02/18, HDFFV-9670)
- Problem Reading Chunked Datasets with a String Datatype Larger
Than the Chunk Size in Bytes
When the latest file format was used and when a chunked dataset
was created with a datatype with the size bigger than a chunk
size, the data could not be read back. The issue was reported
for chunked datasets with a string datatype and was confirmed
for other datatypes with the sizes bigger than the chunk size in
bytes.
Fixed.
(JM - 2016/02/13, HDFFV-9672)
- Control over the Location of External Files
Users were unable to specify the locations of external files.
Two APIs - H5Pget_efile_prefix and H5Pset_efile_prefix - were
added so that users could specify the locations of external files.
(DER - 2016/02/04, HDFFV-8740)
Issues Addressed in this Release Since alpha0
=============================================
- h5format_convert
The h5format_convert tool did not downgrade the version of the
superblock.
Fixed. The tool now will downgrade the version of the superblock.
(EIP 2016/01/11)
- Crashes with multiple threads: invalid pointers
It was reported that alpha0 crashed when used with multiple
threads. The issue exists in the HDF5 Library versions 1.8 and
1.9. The problem is related to a shared file pointer used in some
miscellaneous data structures. The thread-safe library exposed
paths in the library where a file pointer became invalid.
The alpha1 release contains the fixes for the specific use case
as described in HDFFV-9643. We will keep working on identifying
and fixing other paths in the library with similar problems.
(EIP - 2016/01/15, HDFFV-9643)
Supported Platforms
===================
The following platforms are supported and have been tested for this release.
They are built with the configure process unless specified otherwise.
AIX 6.1 xlc/xlc_r 10.1.0.5
(NASA G-ADA) xlC/xlC_r 10.1.0.5
xlf90/xlf90_r 12.1.0.6
Linux 2.6.32-573.22.1.el6 GNU C (gcc), Fortran (gfortran), C++ (g++)
#1 SMP x86_64 GNU/Linux compilers:
(mayll/platypus) Version 4.4.7 20120313 (Red Hat 4.4.7-16)
Version 4.9.3, Version 5.2.0
PGI C, Fortran, C++ for 64-bit target on
x86-64;
Version 15.7-0
Intel(R) C (icc), C++ (icpc), Fortran (icc)
compilers:
Version 15.0.3.187 Build 20150407
MPICH 3.1.4 compiled with GCC 4.9.3
Linux 2.6.32-573.18.1.el6.ppc64 gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11)
#1 SMP ppc64 GNU/Linux g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11)
(ostrich) GNU Fortran (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11)
IBM XL C/C++ V13.1
IBM XL Fortran V15.1
Linux 3.10.0-327.10.1.el7 GNU C (gcc), Fortran (gfortran), C++ (g++)
#1 SMP x86_64 GNU/Linux compilers:
(kituo/moohan) Version 4.8.5 20150623 (Red Hat 4.8.5-4)
Version 4.9.3, Version 5.2.0
Intel(R) C (icc), C++ (icpc), Fortran (icc)
compilers:
Version 15.0.3.187 Build 20150407
MPICH 3.1.4 compiled with GCC 4.9.3
SunOS 5.11 32- and 64-bit Sun C 5.12 SunOS_sparc
(emu) Sun Fortran 95 8.6 SunOS_sparc
Sun C++ 5.12 SunOS_sparc
Windows 7 Visual Studio 2012 w/ Intel Fortran 15 (cmake)
Visual Studio 2013 w/ Intel Fortran 15 (cmake)
Visual Studio 2015 w/ Intel Fortran 16 (cmake)
Cygwin(CYGWIN_NT-6.1 2.2.1(0.289/5/3) gcc(4.9.3) compiler and gfortran)
(cmake and autotools)
Windows 7 x64 Visual Studio 2012 w/ Intel Fortran 15 (cmake)
Visual Studio 2013 w/ Intel Fortran 15 (cmake)
Visual Studio 2015 w/ Intel Fortran 16 (cmake)
Windows 8.1 Visual Studio 2012 w/ Intel Fortran 15 (cmake)
Visual Studio 2013 w/ Intel Fortran 15 (cmake)
Windows 8.1 x64 Visual Studio 2012 w/ Intel Fortran 15 (cmake)
Visual Studio 2013 w/ Intel Fortran 15 (cmake)
Mac OS X Mt. Lion 10.8.5 Apple clang/clang++ version 5.1 from Xcode 5.1
64-bit gfortran GNU Fortran (GCC) 4.8.2
(swallow/kite) Intel icc/icpc/ifort version 15.0.3
Mac OS X Mavericks 10.9.5 Apple clang/clang++ version 6.0 from Xcode 6.2
64-bit gfortran GNU Fortran (GCC) 4.9.2
(wren/quail) Intel icc/icpc/ifort version 15.0.3
Mac OS X Yosemite 10.10.5 Apple clang/clang++ version 6.0 from Xcode 7.0
64-bit gfortran GNU Fortran (GCC) 4.9.2
(osx1010dev/osx1010test) Intel icc/icpc/ifort version 15.0.3
Mac OS X El Capitan 10.11.4 Apple clang/clang++ version 7.3.0 from Xcode 7.3
64-bit gfortran GNU Fortran (GCC) 5.2.0
(osx1010dev/osx1010test) Intel icc/icpc/ifort version 15.0.3
Tested Configuration Features Summary
=====================================
In the tables below
y = tested
n = not tested in this release
C = Cluster
W = Workstation
x = not working in this release
dna = does not apply
( ) = footnote appears below second table
<blank> = testing incomplete on this feature or platform
Platform C F90/ F90 C++ zlib SZIP
parallel F2003 parallel
SunOS 5.11 32-bit n y/y n y y y
SunOS 5.11 64-bit n y/y n y y y
Windows 7 y y/y n y y y
Windows 7 x64 y y/y n y y y
Windows 7 Cygwin n y/y n y y n
Windows 8.1 n y/y n y y y
Windows 8.1 x64 n y/y n y y y
Mac OS X Mountain Lion 10.8.5 64-bit n y/y n y y y
Mac OS X Mavericks 10.9.5 64-bit n y/y n y y y
Mac OS X Yosemeti 10.10.5 64-bit n y/y n y y y
AIX 6.1 32- and 64-bit n y/n n y y y
CentOS 6.7 Linux 2.6.32 x86_64 GNU y y/y y y y y
CentOS 6.7 Linux 2.6.32 x86_64 Intel n y/y n y y y
CentOS 6.7 Linux 2.6.32 x86_64 PGI n y/y n y y y
CentOS 7.1 Linux 3.10.0 x86_64 GNU y y/y y y y y
CentOS 7.1 Linux 3.10.0 x86_64 Intel n y/y n y y y
Linux 2.6.32-431.11.2.el6.ppc64 n y/n n y y y
Platform Shared Shared Shared Thread-
C libs F90 libs C++ libs safe
SunOS 5.11 32-bit y y y y
SunOS 5.11 64-bit y y y y
Windows 7 y y y y
Windows 7 x64 y y y y
Windows 7 Cygwin n n n y
Windows 8.1 y y y y
Windows 8.1 x64 y y y y
Mac OS X Mountain Lion 10.8.5 64-bit y n y y
Mac OS X Mavericks 10.9.5 64-bit y n y y
Mac OS X Yosemeti 10.10.5 64-bit y n y y
AIX 6.1 32- and 64-bit y n n y
CentOS 6.7 Linux 2.6.32 x86_64 GNU y y y y
CentOS 6.7 Linux 2.6.32 x86_64 Intel y y y y
CentOS 6.7 Linux 2.6.32 x86_64 PGI y y y y
CentOS 7.1 Linux 3.10.0 x86_64 GNU y y y y
CentOS 7.1 Linux 3.10.0 x86_64 Intel y y y y
Linux 2.6.32-431.11.2.el6.ppc64 y y y y
Compiler versions for each platform are listed in the preceding
"Supported Platforms" table.
More Tested Platforms
=====================
The following platforms are not supported but have been tested for this release.
Linux 2.6.18-431.11.2.el6 g95 (GCC 4.0.3 (g95 0.94!)
#1 SMP x86_64 GNU/Linux
(platypus)
Windows 7 Visual Studio 2008 (cmake)
Windows 7 x64 Visual Studio 2008 (cmake)
Windows 7 x64 Visual Studio 2010 (cmake) with SWMR using GPFS
Windows 10 Visual Studio 2013 w/ Intel Fortran 15 (cmake)
Windows 10 x64 Visual Studio 2013 w/ Intel Fortran 15 (cmake)
Debian7.5.0 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
gcc (Debian 4.7.2-5) 4.7.2
GNU Fortran (Debian 4.7.2-5) 4.7.2
(cmake and autotools)
Fedora20 3.15.3-200.fc20.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux
gcc (GCC) 4.8.3 20140624 (Red Hat 4.8.3-1)
GNU Fortran (GCC) 4.8.3 20140624 (Red Hat 4.8.3-1)
(cmake and autotools)
SUSE 13.1 3.11.10-17-desktop #1 SMP PREEMPT x86_64 x86_64 x86_64 GNU/Linux
gcc (SUSE Linux) 4.8.1
GNU Fortran (SUSE Linux) 4.8.1
(cmake and autotools)
Ubuntu 14.04 3.13.0-35-generic #62-Ubuntu SMP x86_64 GNU/Linux
gcc (Ubuntu/Linaro 4.9.1-0ubuntu1) 4.9.1
GNU Fortran (Ubuntu/Linaro 4.9.1-0ubuntu1) 4.9.1
(cmake and autotools)
hopper.nersc.gov PrgEnv-gnu/5.2.40
gcc (GCC) 4.9.2 20141030 (Cray Inc.)
GNU Fortran (GCC) 4.9.2 20141030 (Cray Inc.)
g++ (GCC) 4.9.2 20141030 (Cray Inc.)
Known Problems and Limitations
==============================
This section contains the list of known problems and limitations introduced
in this release of HDF5.
Note: this list is not exhaustive of all known issues discovered in HDF5
software to date. For a list of significant problems and known workarounds
identified in past releases, please refer to:
https://www.hdfgroup.org/HDF5/release/known_problems/
The HDF Group also maintains a JIRA issue-tracking database which is used to
capture all known issues which are too numerous to reasonably list in this
document. The HDF Group is taking steps to make our JIRA issue database
open to the public, and this section will refer to that database in a future
release. In the meantime, please contact help@hdfgroup.org if you come across
an issue not listed here or at the link above, and we will provide any
information about known workarounds that we have or add it to our list of
known issues if it is a new issue.
- The flush/refresh test occasionally fails on OS X platforms. This is
being investigated but no fix or workaround is available at this time.
(DER - 2016/03/22, HDFFV-9731)
- The VDS/SWMR test will fail with a segmentation fault if the library
is built with --enable-using-memchecker. The is due to a VDS shutdown
procedure freeing a shared resource too early when the memory
checker changes are built. This problem does not arise when the
memory checker changes are not used since the internal library free
lists behave differently. The memory checker configure option should
normally only be used under special circumstances so this should not
affect most users. Users should be aware that the --enable-using-memchecker
+ VDS combination may cause a segfault, however, so Valgrind et al. may
have to be used with an HDF5 library built without the feature if this
proves to be a problem.
(DER - 2016/03/21, HDFFV-9732)
- SWMR feature limitations
The SWMR feature will only work if an HDF5 file under SWMR access resides
on a file system that obeys POSIX write() ordering semantics. Because of
this, SWMR will not work on network file systems such as NFS or SMB/Windows
file shares since those systems do not guarantee write odering. SWMR
regression tests are likely to fail if run on a network file system. SWMR
is currently not tested on Windows though it can be tested manually
(some of the SWMR test programs are built by CMake), and there are no
obvious reasons for it to not work on NTFS or GPFS.
(EIP - 2016/03/20, HDFFV-9733)
- VDS feature limitation
Currently, the path to a VDS source file is interpreted as relative to the
directory where the executable program runs and not to the HDF5 file with
the VDS dataset unless a full path to the source file is specified during
the mapping.
(EIP - 2016/03/20, HDFFV-9724)
- The H5Lexists API changed behavior in HDF5-1.10 when used with a file handle
and root group name ("/"):
H5Lexists(fileid, "/")
In HDF5-1.8 it returns false (0) and in HDF5-1.10 it returns true (1).
The documentation will be updated with information regarding this change.
(LRK - 2016/03/30, HDFFV-8746)
%%%%1.10.0%%%%
HDF5 version 1.10.0 released on 2016-03-30
================================================================================
INTRODUCTION
This document describes the differences between HDF5-1.8 series and
HDF5 1.10.0 releases, and contains information on the platforms
tested.
Links to HDF5 1.10.0 source code can be found on The HDF Group's
development FTP server at the following location:
https://www.hdfgroup.org/HDF5/release/obtain5110.html
User documentation can be accessed directly at this location:
https://www.hdfgroup.org/HDF5/docNewFeatures/
For more information, see the HDF5 home page:
https://www.hdfgroup.org/HDF5/
If you have any questions or comments, please send them to the HDF
Help Desk:
help@hdfgroup.org
CONTENTS
- New Features
- Issues Addressed in this Release
- Supported Platforms
- Tested Configuration Features Summary
- More Tested Platforms
- Known Problems and Limitations
New Features
============
This release supports the following features:
Configuration
-------------
- API Compatibility with HDF5 1.8 Flag Was Added
The 1.10 version of the HDF5 Library can be configured to operate
identically to the 1.8 library with the --with-default-api-version=v18
configure flag. This allows existing code to be compiled with the 1.10
library without requiring immediate changes to the application source
code. For addtional configuration options and other details, see
"API Compatibility Macros in HDF5" at
https://www.hdfgroup.org/HDF5/doc/RM/APICompatMacros.html.
- Autotools Configuration Has Been Extensively Reworked
The autotools configuration options have been updated to allow more
fine-grained control of the build options and to correct some bugs.
See configure --help for comprehensive information on each option.
Specific changes:
* --enable-debug and --enable-production are no longer accepted.
Use --enable-build-mode=(debug | production) instead. These set
appropriate defaults for symbols, optimizations, and other
configuration options. These defaults can be overridden by the
user.
* Extra debug output messages are no longer enabled with
--enable-debug=<package list>. Use --enable-internal-debug=<pkg list>
instead.
* A new --enable-symbols option allows symbols to be generated
independently of the build mode. --disable-symbols can be used
to strip symbols from the binary.
* A new --enable-asserts option sets/unsets NDEBUG. This is
independent of the build mode. This also enables some extra
low-overhead debug checks in the library.
* A new --enable-profiling option sets profiling flags. This is
independent of the build mode.
* A new --enable-optimization option sets the optimization level.
This is independent of the build mode.
* Many of these options can take a flags string that will be used
to build the library. This can be useful for specifying custom
optimization flags such as -Os and -Ofast.
* gnu C++ and Fortran use configure sub-files that update the
build flags and turn on warnings. The increase in warnings when
building these wrapper libraries is due to these flag changes
and not to a decrease in code quality.
* The option to clear file buffers has been removed. Any buffer that
will eventually be written to disk will now always be memset
to zero. This prevents the previous contents of the buffer from
being written to the disk if the buffer contents are not
completely overwritten, which has security implications.
- LFS Changes
The way the autotools handle large file support (LFS) has been
overhauled in this release.
* We assume ftello and fseeko exist
* We no longer explicitly use the *64 I/O functions. Instead, we
rely on a mapping provided by _FILE_OFFSET_BITS or its equivalent.
* _LARGEFILE(64)_SOURCE is no longer exported via AM_CPPFLAGS.
Parallel Library
-----------------
- Collective Metadata I/O
Calls for HDF5 metadata can result in many small reads and writes.
On metadata reads, collective metadata I/O can improve performance
by allowing the library to perform optimizations when reading the
metadata by having one rank read the data and broadcasting it to
all other ranks.
Collective metadata I/O improves metadata write performance through
the construction of an MPI derived datatype that is then written
collectively in a single call. For more information, see
https://www.hdfgroup.org/HDF5/docNewFeatures/NewFeaturesCollectiveMetadataIoDocs.html.
Library
--------
- Concurrent Access to HDF5 Files - Single Writer/ Multple Reader (SWMR)
The Single Writer/ Multiple Reader or SWMR feature enables users to
read data concurrently while writing it. Communications between the
processes and file locking are not required. The processes can run
on the same or on different platforms as long as they share a common
file system that is POSIX compliant. For more information, see the
Single-Writer/Multiple-Reader (SWMR) documentation at
https://www.hdfgroup.org/HDF5/docNewFeatures/NewFeaturesSwmrDocs.html.
- Virtual Dataset (VDS)
The VDS feature enables data to be accessed across HDF5 files
using standard HDF5 objects such as groups and datasets without
rewriting or rearranging the data. An HDF5 virtual dataset (VDS)
is an HDF5 dataset that is composed of source HDF5 datasets in
a predefined mapping. VDS can be used with the SWMR feature. For
documentation, check
https://www.hdfgroup.org/HDF5/docNewFeatures/NewFeaturesVirtualDatasetDocs.html.
- Persistent Free File Space Tracking
Usage patterns when working with an HDF5 file sometimes result in
wasted space within the file. This can also impair access times
when working with the resulting files. The new file space management
feature provides strategies for managing space in a file to improve
performance in both of these areas. For more information, see
https://www.hdfgroup.org/HDF5/docNewFeatures/NewFeaturesFileSpaceMgmtDocs.html.
- Version 3 Metadata Cache
The version 3 metadata cache moves management of metadata I/O from
the clients to the metadata cache proper. This change is essential for
SWMR and other features that have yet to be released.
C++ Library
------------
- New Member Function Added to H5::ArrayType
The assignment operator ArrayType::operator= was added because
ArrayType has pointer data members.
(BMR - 2016/03/07, HDFFV-9562)
Tools
------
- h5watch
The h5watch tool allows users to output new records appended to
a dataset under SWMR access as it grows. The functionality is
similar to the Unix user command "tail" with the follow option,
which outputs appended data as the file grows. For more
information, see
https://www.hdfgroup.org/HDF5/docNewFeatures/NewFeaturesSwmrDocs.html#Tools.
- h5format_convert
The h5format_convert tool allows users to convert the indexing
type of a chunked dataset made with a 1.10.x version of the HDF5
Library when the latest file format is used to the 1.8.x version 1 B-tree indexing
type. For example, datasets created using SWMR access, can be
converted to be accessed by the HDF5 1.18 library and tools. The
tool does not rewrite raw data, but it does rewrite HDF5 metadata.
High-Level APIs
----------------
- H5DOappend
The function appends data to a dataset along a specified dimension.
C Packet Table API
------------------
- Replacement of a Public Function with H5PTcreate
The existing function H5PTcreate_fl limits applications so they
can use the deflate compression only. The public function
H5PTcreate has been added to replace H5PTcreate_fl. H5PTcreate
takes a property list identifier to provide flexibility on
creation properties.
(BMR - 2016/03/04, HDFFV-8623)
- New Public Functions: H5PTget_dataset and H5PTget_type
Two accessor functions have been added. H5PTget_dataset returns
the identifier of the dataset associated with the packet table,
and H5PTget_type returns the identifier of the datatype used by
the packet table.
(BMR, 2016/03/04, HDFFV-8623)
- Regarding #ifdef VLPT_REMOVED
The #ifdef VLPT_REMOVED blocks have been removed from the packet
table (PT) library source except for the following functions:
+ H5PTis_varlen() has been made available again
+ H5PTfree_vlen_readbuff() is now H5PTfree_vlen_buff()
(BMR - 2016/03/04, HDFFV-442)
C++ Packet Table API
--------------------
- New Constructor Added to FL_PacketTable
An overloaded constructor has been added to FL_PacketTable and
takes a property list identifier to provide flexibility on
creation properties.
(BMR - 2016/03/08, HDFFV-8623)
- New Public Functions
Two accessor wrappers are added to class PacketTable.
PacketTable::GetDataset() returns the identifier of the dataset
associated with the packet table, and PacketTable::GetDatatype()
returns the identifier of the datatype that the packet table uses.
(BMR - 2016/03/04, HDFFV-8623)
- Member Functions with "char*" as an Argument
Overloaded functions were added to provide the "const char*"
argument; the existing version will be deprecated in future
releases.
(BMR - 2016/03/04, HDFFV-8623)
- Regarding #ifdef VLPT_REMOVED
The #ifdef VLPT_REMOVED blocks have been removed from the packet
table library source code except for the following functions:
+ VL_PacketTable::IsVariableLength() was moved to PacketTable
+ VL_PacketTable::FreeReadBuff() is now PacketTable::FreeBuff()
(BMR - 2016/03/04, HDFFV-442)
Java Wrapper Library
--------------------
The Java HDF5 JNI library has been integrated into the HDF5 repository.
The configure option is "--enable-java", and the CMake option is
HDF5_BUILD_JAVA:BOOL=ON. The package hierarchy has changed from the
HDF5 1.8 JNI, which was "ncsa.hdf.hdflib.hdf5", to HDF5 1.10,
"hdf.hdflib.hdf5".
A number of new APIs were added including some for VDS and SWMR.
Other Important Changes
-----------------------
The hid_t type was changed from 32-bit to a 64-bit value.
Issues Addressed in this Release Since alpha1
=============================================
- H5Pget_virtual_printf_gap, H5Pget_virtual_view, H5Pget_efile_prefix
The correct access property list settings from the
H5Pget_virtual_printf_gap, H5Pget_virtual_view, and
H5Pget_efile_prefix function calls could not be retrieved
using H5Dget_access_plist().
Fixed.
(DER and NAF - 2016/03/14, HDFFV-9716)
- h5dump
When h5dump was provided with the name of a non-existing file or
when optional arguments were the last option on the command line,
h5dump would segfault.
Fixed.
(ADB 2016/02/28 HDFFV-9639, HDFFV-9684)
- No Error Message for Corrupt Metadata
The HDF5 Library did not propagate an error when it encountered
corrupt metadata in an HDF5 file. The issue was fixed for a
specific file provided by a user. If you still see the problem,
please contact help@hdfgroup.org
Fixed.
(MC - 2016/02/18, HDFFV-9670)
- Problem Reading Chunked Datasets with a String Datatype Larger
Than the Chunk Size in Bytes
When the latest file format was used and when a chunked dataset
was created with a datatype with the size bigger than a chunk
size, the data could not be read back. The issue was reported
for chunked datasets with a string datatype and was confirmed
for other datatypes with the sizes bigger than the chunk size in
bytes.
Fixed.
(JM - 2016/02/13, HDFFV-9672)
- Control over the Location of External Files
Users were unable to specify the locations of external files.
Two APIs - H5Pget_efile_prefix and H5Pset_efile_prefix - were
added so that users could specify the locations of external files.
(DER - 2016/02/04, HDFFV-8740)
Issues Addressed in this Release Since alpha0
=============================================
- h5format_convert
The h5format_convert tool did not downgrade the version of the
superblock.
Fixed. The tool now will downgrade the version of the superblock.
(EIP 2016/01/11)
- Crashes with multiple threads: invalid pointers
It was reported that alpha0 crashed when used with multiple
threads. The issue exists in the HDF5 Library versions 1.8 and
1.9. The problem is related to a shared file pointer used in some
miscellaneous data structures. The thread-safe library exposed
paths in the library where a file pointer became invalid.
The alpha1 release contains the fixes for the specific use case
as described in HDFFV-9643. We will keep working on identifying
and fixing other paths in the library with similar problems.
(EIP - 2016/01/15, HDFFV-9643)
Supported Platforms
===================
The following platforms are supported and have been tested for this release.
They are built with the configure process unless specified otherwise.
AIX 6.1 xlc/xlc_r 10.1.0.5
(NASA G-ADA) xlC/xlC_r 10.1.0.5
xlf90/xlf90_r 12.1.0.6
Linux 2.6.32-573.18.1.el6 GNU C (gcc), Fortran (gfortran), C++ (g++)
#1 SMP x86_64 GNU/Linux compilers:
(mayll/platypus) Version 4.4.7 20120313 (Red Hat 4.4.7-16)
Version 4.9.3, Version 5.2.0
PGI C, Fortran, C++ for 64-bit target on
x86-64;
Version 15.7-0
Intel(R) C (icc), C++ (icpc), Fortran (icc)
compilers:
Version 15.0.3.187 Build 20150407
MPICH 3.1.4 compiled with GCC 4.9.3
Linux 2.6.32-504.8.1.el6.ppc64 gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11)
#1 SMP ppc64 GNU/Linux g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11)
(ostrich) GNU Fortran (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11)
IBM XL C/C++ V13.1
IBM XL Fortran V15.1
Linux 3.10.0-327.10.1.el7 GNU C (gcc), Fortran (gfortran), C++ (g++)
#1 SMP x86_64 GNU/Linux compilers:
(kituo/moohan) Version 4.8.5 20150623 (Red Hat 4.8.5-4)
Version 4.9.3, Version 5.2.0
Intel(R) C (icc), C++ (icpc), Fortran (icc)
compilers:
Version 15.0.3.187 Build 20150407
MPICH 3.1.4 compiled with GCC 4.9.3
SunOS 5.11 32- and 64-bit Sun C 5.12 SunOS_sparc
(emu) Sun Fortran 95 8.6 SunOS_sparc
Sun C++ 5.12 SunOS_sparc
Windows 7 Visual Studio 2012 w/ Intel Fortran 15 (cmake)
Visual Studio 2013 w/ Intel Fortran 15 (cmake)
Visual Studio 2015 w/ Intel Fortran 16 (cmake)
Cygwin(CYGWIN_NT-6.1 2.2.1(0.289/5/3) gcc(4.9.3) compiler and gfortran)
(cmake and autotools)
Windows 7 x64 Visual Studio 2012 w/ Intel Fortran 15 (cmake)
Visual Studio 2013 w/ Intel Fortran 15 (cmake)
Visual Studio 2015 w/ Intel Fortran 16 (cmake)
Windows 8.1 Visual Studio 2012 w/ Intel Fortran 15 (cmake)
Visual Studio 2013 w/ Intel Fortran 15 (cmake)
Windows 8.1 x64 Visual Studio 2012 w/ Intel Fortran 15 (cmake)
Visual Studio 2013 w/ Intel Fortran 15 (cmake)
Mac OS X Mt. Lion 10.8.5 Apple clang/clang++ version 5.1 from Xcode 5.1
64-bit gfortran GNU Fortran (GCC) 4.8.2
(swallow/kite) Intel icc/icpc/ifort version 15.0.3
Mac OS X Mavericks 10.9.5 Apple clang/clang++ version 6.0 from Xcode 6.2.0
64-bit gfortran GNU Fortran (GCC) 4.9.2
(wren/quail) Intel icc/icpc/ifort version 15.0.3
Mac OS X Yosemite 10.10.5 Apple clang/clang++ version 6.0 from Xcode 7.0.0
64-bit gfortran GNU Fortran (GCC) 4.9.2
(osx1010dev/osx1010test) Intel icc/icpc/ifort version 15.0.3
Mac OS X El Capitan 10.11.3 Apple clang/clang++ version 7.0.2 from Xcode 7.0.2
64-bit gfortran GNU Fortran (GCC) 5.2.0
(osx1010dev/osx1010test) Intel icc/icpc/ifort version 15.0.3
Tested Configuration Features Summary
=====================================
In the tables below
y = tested
n = not tested in this release
C = Cluster
W = Workstation
x = not working in this release
dna = does not apply
( ) = footnote appears below second table
<blank> = testing incomplete on this feature or platform
Platform C F90/ F90 C++ zlib SZIP
parallel F2003 parallel
SunOS 5.11 32-bit n y/y n y y y
SunOS 5.11 64-bit n y/y n y y y
Windows 7 y y/y n y y y
Windows 7 x64 y y/y n y y y
Windows 7 Cygwin n y/y n y y n
Windows 8.1 n y/y n y y y
Windows 8.1 x64 n y/y n y y y
Mac OS X Mountain Lion 10.8.5 64-bit n y/y n y y y
Mac OS X Mavericks 10.9.5 64-bit n y/y n y y y
Mac OS X Yosemeti 10.10.5 64-bit n y/y n y y y
AIX 6.1 32- and 64-bit n y/n n y y y
CentOS 6.7 Linux 2.6.32 x86_64 GNU y y/y y y y y
CentOS 6.7 Linux 2.6.32 x86_64 Intel n y/y n y y y
CentOS 6.7 Linux 2.6.32 x86_64 PGI n y/y n y y y
CentOS 7.1 Linux 3.10.0 x86_64 GNU y y/y y y y y
CentOS 7.1 Linux 3.10.0 x86_64 Intel n y/y n y y y
Linux 2.6.32-431.11.2.el6.ppc64 n y/n n y y y
Platform Shared Shared Shared Thread-
C libs F90 libs C++ libs safe
SunOS 5.11 32-bit y y y y
SunOS 5.11 64-bit y y y y
Windows 7 y y y y
Windows 7 x64 y y y y
Windows 7 Cygwin n n n y
Windows 8.1 y y y y
Windows 8.1 x64 y y y y
Mac OS X Mountain Lion 10.8.5 64-bit y n y y
Mac OS X Mavericks 10.9.5 64-bit y n y y
Mac OS X Yosemeti 10.10.5 64-bit y n y y
AIX 6.1 32- and 64-bit y n n y
CentOS 6.7 Linux 2.6.32 x86_64 GNU y y y y
CentOS 6.7 Linux 2.6.32 x86_64 Intel y y y y
CentOS 6.7 Linux 2.6.32 x86_64 PGI y y y y
CentOS 7.1 Linux 3.10.0 x86_64 GNU y y y y
CentOS 7.1 Linux 3.10.0 x86_64 Intel y y y y
Linux 2.6.32-431.11.2.el6.ppc64 y y y y
Compiler versions for each platform are listed in the preceding
"Supported Platforms" table.
More Tested Platforms
=====================
The following platforms are not supported but have been tested for this release.
Linux 2.6.18-431.11.2.el6 g95 (GCC 4.0.3 (g95 0.94!)
#1 SMP x86_64 GNU/Linux
(platypus)
Windows 7 Visual Studio 2008 (cmake)
Windows 7 x64 Visual Studio 2008 (cmake)
Windows 7 x64 Visual Studio 2010 (cmake) with SWMR using GPFS
Windows 10 Visual Studio 2013 w/ Intel Fortran 15 (cmake)
Windows 10 x64 Visual Studio 2013 w/ Intel Fortran 15 (cmake)
Debian7.5.0 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
gcc (Debian 4.7.2-5) 4.7.2
GNU Fortran (Debian 4.7.2-5) 4.7.2
(cmake and autotools)
Fedora20 3.15.3-200.fc20.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux
gcc (GCC) 4.8.3 20140624 (Red Hat 4.8.3-1)
GNU Fortran (GCC) 4.8.3 20140624 (Red Hat 4.8.3-1)
(cmake and autotools)
SUSE 13.1 3.11.10-17-desktop #1 SMP PREEMPT x86_64 x86_64 x86_64 GNU/Linux
gcc (SUSE Linux) 4.8.1
GNU Fortran (SUSE Linux) 4.8.1
(cmake and autotools)
Ubuntu 14.04 3.13.0-35-generic #62-Ubuntu SMP x86_64 GNU/Linux
gcc (Ubuntu/Linaro 4.9.1-0ubuntu1) 4.9.1
GNU Fortran (Ubuntu/Linaro 4.9.1-0ubuntu1) 4.9.1
(cmake and autotools)
hopper.nersc.gov PrgEnv-gnu/5.2.40
gcc (GCC) 4.9.2 20141030 (Cray Inc.)
GNU Fortran (GCC) 4.9.2 20141030 (Cray Inc.)
g++ (GCC) 4.9.2 20141030 (Cray Inc.)
Known Problems and Limitations
==============================
This section contains the list of known problems and limitations introduced
in this release of HDF5.
Note: this list is not exhaustive of all known issues discovered in HDF5
software to date. For a list of significant problems and known workarounds
identified in past releases, please refer to:
https://www.hdfgroup.org/HDF5/release/known_problems/
The HDF Group also maintains a JIRA issue-tracking database which is used to
capture all known issues which are too numerous to reasonably list in this
document. The HDF Group is taking steps to make our JIRA issue database
open to the public, and this section will refer to that database in a future
release. In the meantime, please contact help@hdfgroup.org if you come across
an issue not listed here or at the link above, and we will provide any
information about known workarounds that we have or add it to our list of
known issues if it is a new issue.
- The JUnit-interface test may fail on Solaris platforms. The result of
a test for verifying the content of the error stack to stdout is
in a different order on Solaris then other platforms. Use make -i option
to test beyond the java/test folder.
(ADB - 2016/03/22, HDFFV-9734)
- The flush/refresh test occasionally fails on OS X platforms. This is
being investigated but no fix or workaround is available at this time.
(DER - 2016/03/22, HDFFV-9731)
- The VDS/SWMR test will fail with a segmentation fault if the library
is built with --enable-using-memchecker. The is due to a VDS shutdown
procedure freeing a shared resource too early when the memory
checker changes are built. This problem does not arise when the
memory checker changes are not used since the internal library free
lists behave differently. The memory checker configure option should
normally only be used under special circumstances so this should not
affect most users. Users should be aware that the --enable-using-memchecker
+ VDS combination may cause a segfault, however, so Valgrind et al. may
have to be used with an HDF5 library built without the feature if this
proves to be a problem.
(DER - 2016/03/21, HDFFV-9732)
- SWMR feature limitations
The SWMR feature will only work if an HDF5 file under SWMR access resides
on a file system that obeys POSIX write() ordering semantics. Because of
this, SWMR will not work on network file systems such as NFS or SMB/Windows
file shares since those systems do not guarantee write odering. SWMR
regression tests are likely to fail if run on a network file system. SWMR
is currently not tested on Windows though it can be tested manually
(some of the SWMR test programs are built by CMake), and there are no
obvious reasons for it to not work on NTFS or GPFS.
(EIP - 2016/03/20, HDFFV-9733)
- VDS feature limitation
Currently, the path to a VDS source file is interpreted as relative to the
directory where the executable program runs and not to the HDF5 file with
the VDS dataset unless a full path to the source file is specified during
the mapping.
(EIP - 2016/03/20, HDFFV-9724)
- When building HDF5 with Java using CMake and specifying Debug for CMAKE_BUILD_TYPE,
there is a missing command argument for the tests of the examples.
This error can be avoided by not building Java with Debug, HDF5_BUILD_JAVA:BOOL=OFF,
or not building Examples, HDF5_BUILD_EXAMPLES:BOOL=OFF.
(LRK - 2016/03/30, HDFFV-9743)
- The H5Lexists API changed behavior in HDF5-1.10 when used with a file handle
and root group name ("/"):
H5Lexists(fileid, "/")
In HDF5-1.8 it returns false (0) and in HDF5-1.10 it returns true (1).
The documentation will be updated with information regarding this change.
(LRK - 2016/03/30, HDFFV-8746)
|
