summaryrefslogtreecommitdiffstats
path: root/tools/h5dump
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r18055] Bug fix: 1192Albert Cheng2009-12-262-11/+18
| | | | | | | | Description: Fixed exit code (sometimes return code in Main) to follow the HDF5 standards. Tested: H5committested plus serial test in Jam.
* [svn-r18011] Description:Quincey Koziol2009-12-131-17/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bring Coverity changes into the trunk: (also other minor cleanups) r17991: Fix Coverity items 175 and 176. Fixed memory leak on error in print_enum in H5LT.c. r17993: (r17992 was not a Coverity change) Close Coverity issue #206: inconsistently checking whether dt->shared was non-NULL after H5T_alloc() returned a valid 'dt' value (which should guarantee that dt->shared is valid). r17994: Fix Coverity item 149. Fixed file handle leak on error in H5FD_stdio_open. r17995: Fixed Coverity issues 154 to 161: Added H5MP_close routine to error handling in the event *mp has not been freed before error. r17996: Close Coverity issue #126: potentially leaking merged_spans on routine failure. r17997: Fix Coverity items 147 and 148. Fixed resource leaks on error in H5FDloc.c. r17998: Coverity issue 269-272: Added integer result variable to functions that could return negative. Assigned to unsigned after checking. Added H5E_BEGIN_TRY block around H5Tclose and removed H5E_THROW in the catch block. Checked buffer is NULL before free. Changed HGOTO_ERROR outside of the if block to H5E_THROW. r17999: Close Coverity issue #127: release temporary spans in more generic manner. (Also add error checking to previous fix) r18000: Resolved Coverity issues 211 and 212 in H5T.c. Added comments to ignore Coverity warning regarding not checking pointer for NULL, as we are using an assert which catches the issue. r18001: Fix Coverity item 146. Fixed resource leak on error in H5O_layout_copy. r18002: Fix Coverity items 143 and 145. Fixed resource leaks on error in H5D_compact_copy and H5D_contig_copy. r18003: Close Coverity issue #192: close file on error r18004: Fix Coverity issue #125: release temporary spans on error r18005: Resolved Coverity issues 5, 25, and 83 (in H5T.c): Separated embedded functions in order to check for NULL on return of H5I_object before passing into H5T_copy. Check to see if new_dt is NULL within error handling before dereferencing it. Ignore Coverity's dead code warnings as the checks that lead to the code are machine dependent. r18006: Coverity 63,70,73: Checked result of function before assigning to an unsigned variable. r18007: Coverity 78,79: added continue statement if H5Pget_filter2 returns negative. r18008: Fixed Coverity issue # 138: Added support in error handling to free dst pointer (if allocated) on error. r18009: Whitespace & coding style cleanup
* [svn-r17953] Description:Quincey Koziol2009-12-032-30/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bring Coverity changes into the trunk: r17877: Error 266: Uninitialized memspace set to -1. Changed malloc and free to HDmalloc and HDfree. Removed unused dtype var. r17878: Error 265: Uninitialized mem_space set to -1. Changed malloc and free to HDmalloc and HDfree. Error 267: Uninitialized smspace set to -1. Changed malloc and free to HDmalloc and HDfree. r17879: Error 242: Uninitialized aid set to -1. Error 243: Uninitialized sid set to -1. Uninitialized tid set to -1 for consistency r17880: Error 242: reinitialized aid to -1 after close to be ready for reuse. Error 243: reinitialized sid to -1 after close to be ready for reuse. reinitialized tid to -1 for consistency after close to be ready for reuse. r17881: use valgrind to check there is a memory leak. The fix is to free ptrstr in line 5838 at xml_dump_group() of h5dump.c after it is used. run the valgrind after the fix, no memory leak for that part of the code. r17882: Fix Coverity items 256 and 269. r17883: Error 222-230: initialized hid_t vars to -1 after close to be ready for reuse. Also added H5Tclose for tid in gent_bigdims r17884: Bug fix (Coverity run2, view 23, dead code) (this is pair-program done by Albert, Elena and Larry). Confirmed and fixed the deadcode in hyperslab read branch of function diff_datasetid. (Discovered other bad code that diff_datasetid() should be recoded. Bug 1693 is entered for this.) r17906: Fix Coverity item 260. r17907: 262: Initialized hid_t's dtype, dtype_tmp and file to -1. Initialized H5T_t * dt to NULL. r17908: Fix Coverity item 261. r17909: Fix Coverity item 248. r17910: Revise fix for Coverity item 248. r17911: Resolved coverity issues #s 263, 162, 163, 164. All issues in dsets.c. Initialized fid and did hid_t's. filter_corrupt function was returning in the middle of an if statement, bypassing free calls. Updated error handling to free buffers and hid_t's appropriately. r17912: (done by Larry and Albert) Cleanup Coverity view warnings (#231-241) about using uninitialized variables. Initialized all of them. r17913: Resolved issue 251 and 264. Initialized tid2 to -1 and initialized buffers that were freed in case of an error. r17914: Resolved coverity issues 66, 220, and 221: 66: Negative Return assignment ignored 220,221: Initialized hid_t's. r17915: Fix Coverity item 247. r17916: Fix Coverity item 246. r17917: Fix Coverity item 245. r17918: Fix Coverity item 244. r17919: Coverity Issue #84: Moved asserts in H5T_cmp to the top of the function, and converted them to HDassert. Coverity complaining about using potentially NULL pointer without checking it. Want to see if Coverity will accept Assertions as acceptable checking before using the value. 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/default API=1.8.x, 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 debug mode Linux/64-amd64 2.6 (abe) w/parallel, w/FORTRAN, in production mode Mac OS X/32 10.6.2 (amazon) in debug mode Mac OS X/32 10.6.2 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode
* [svn-r17616] Purpose:Mike McGreevy2009-10-082-9/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CFLAGS overhaul Description: Modified the way configure handles CFLAGS. (note: all changes also apply to FCFLAGS, CXXFLAGS, CPPFLAGS, and LDFLAGS). 1. The configure process will now always preserve a user's CFLAGS environment variable setup. Any additional flags necessary for compilation added at configure time will be passed into the Makefiles as AM_CFLAGS, which is an automake construct to be used in addition to CFLAGS. This will allow a user to have the final say, as CFLAGS will always appear later in the compile line than AM_CFLAGS. Additionally, setting CFLAGS during make will no longer completely erase all flags set by configure, since they're maintained in AM_CFLAGS. 2. Additionally, where possible, flags previously being assigned directly into CFLAGS (and thus propagating into h5cc) have now been redirected into H5_CFLAGS, so they're used ONLY for compiling hdf5, and not embedded into the h5cc wrapper script as well. *Note that H5_CFLAGS ultimately is assigned into AM_CFLAGS for use in the Makefiles. Complete description of changes and build process will be included in a Configure Document that Elena and I are working on. 3. Removed unsupported config files. This includes: config/dec-osf* config/hpux11.00 config/irix5.x config/powerpc-ibm-aix4.x config/rs6000-ibm-aix5.x config/unicos* 4. Modified configure summary to display additional values. Specifically, appropriate AM_* variables are being shown, as well as H5_FCFLAGS and H5_CXXFLAGS, which were for some reason not already present. Tested: - H5committest - Tested on all THG / NCSA machines, using several combinations of the more prominent configure options (c++, fortran, szip, threadsafe, parallel, et cetera). (Thanks to Quincey for rysnc testing setup!) - With regards to new automated testing, anything *necessary* for compilation will be caught by the daily tests as it stands now. (i.e., if LDFLAGS is not properly set when szip is used, linking will fail). Additionally, with regards to which flags get into h5cc, if any *necessary* flags have been improperly removed, then daily tests should fail during make installcheck. Additional machine-specific desired behaviors and/or checks may have to be set up separately within the daily tests, so this is something to work on.
* [svn-r17606] Code Cleanup:Albert Cheng2009-10-071-12/+4
| | | | | | | | TFLOPS machine has retired long ago. Removed all code specific for its support. Test: h5committested.
* [svn-r17582] Description:Quincey Koziol2009-10-023-10/+56
| | | | | | | | | | | | | | | | | | | | | Bring changes from file free space branch back to the trunk. *yay!* 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/default API=1.8.x, 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 debug mode Linux/64-amd64 2.6 (abe) w/parallel, w/FORTRAN, in production mode Mac OS X/32 10.5.8 (amazon) in debug mode Mac OS X/32 10.5.8 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode
* [svn-r17566] Fix for Bug 1562. H5DSis_attached needed to account for ↵Allen Byrne2009-10-011-2/+0
| | | | | | | | | platform dependent types. Added test and test files for LE and BE dimension scales. Reworked part of test_ds file as part of debug. Added missing H5Tclose in region reference routines. H5DS.c checked for other locations which need to account for platform dependent types in dealing with ds_list_t. Added generator program for test files of LE and BE dimension scales. Tested: local linux, h5committest
* [svn-r17475] Added error handling to h5dump and region reference handling ↵Allen Byrne2009-09-141-0/+3
| | | | | | functions in the tools lib. Bring back from NPOESS. Added missing tests to h5dump test script for region references. Tested: local linux
* [svn-r17454] Bug fix. (Daily test failure).Albert Cheng2009-09-071-2/+2
| | | | | | | Generic function name is used but that would fail when v16API is used. Changed the H5Dcreate() and H5Acreate() to v18 names as H5Dcreate2() and H5Acreate2(). tested: jam (regular and --with-default-api-version=v16).
* [svn-r17450] Bring h5dump single subsetting selection and region reference ↵Allen Byrne2009-09-042-94/+231
| | | | | | changes from NPOESS Tested: local linux smirom
* [svn-r17345] Purpose:Mike McGreevy2009-08-121-49/+97
| | | | | | | | | | | | | | | | | | | | | | | | Updating autotools Description: Installed new autotools and used them to reconfigure HDF5. - Automake upgraded to 1.11 - Autoconf upgraded to 2.64 - bin/reconfigure script edited to use new versions (on jam), and run to generate new configure script and Makefile.in's. - configure.in script edited to add "_cv_" to all AC_CACHE_VAL strings (in order to comply with new autoconf standard). Tested: Tested on machines jam, smirom, liberty, linew. Tested w/ features c++, fortran, parallel. Tested w/ compilers gcc, pgcc, icc. Further testing via Daily Tests should catch any other outliers. Upon passing DT's, I'll propogate the new tools into 1.8, hdf4, et cetera.
* [svn-r17313] Description:Quincey Koziol2009-08-101-14/+12
| | | | | | | | | | | | | | | | | | | | | Bring back various minor code cleanups from the file free space branch 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 (kagiso) 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.8 (amazon) in debug mode Mac OS X/32 10.5.8 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode
* [svn-r17295] Specified HDTarray_create and HDCreate as HDTarray_create2 and ↵Allen Byrne2009-08-031-2/+2
| | | | | | HDCreate2 in gent_array8 function as was done in other gent_arrayX functions. Fixes 1.6 compatibility mode argument errors. Tested: linux
* [svn-r17289] Added test targeted for bug 1520, which was fixed last week. ↵Allen Byrne2009-07-312-37/+57
| | | | | | The test generates an array datatype of ints larger than the display buffer. The bug was exposed when the buffer was reallocated. Tested: linux
* [svn-r17268] Description:Quincey Koziol2009-07-301-6/+6
| | | | | | | | | | | Bring r17266 from 1.8 branch to trunk: Clean up various compiler warnings from IRIX64 build Tested on: Mac OS X/32 (amazon) debug & production (yes, I know it's not an IRIX64 system :-) Too minor to require h5committest
* [svn-r17228] Purpose:Mike McGreevy2009-07-232-1/+10
| | | | | | | | | | | | | | | | | | | | | | | Fix BZ #1583 Description: The --enable-static-exec flag was broken. Configure was adding the -all-static linker flag to an environment variable which was subsequently never used. (looks like it was used in 1.6 Makefile.ins, but never moved to 1.8's Makefile.ams when we added automake support). To fix, I've added this environment varibale to the link lines of all the tools. Now, when --enable-static-exec is invoked, it will correctly generate statically linked executables in the installed bin directory. Tested: I've tested manually to ensure that the generated execs are static when the flag is used and dynamic when not. I've also tested when szip is used, as this was a use case mentioned in the bug report. Also: ran full tests with make check on jam and smirom for good measure.
* [svn-r17075] Implemented nowrap option (Bug 811) equivalent to h5ls tool. ↵Allen Byrne2009-06-171-3/+15
| | | | | | Also updated usage output. Tested: linux
* [svn-r16807] Purpose: Fix bug 1533Neil Fortner2009-04-201-1/+1
| | | | | | | | | | | Description: Previously, there was no versioning for H5Z_class_t. This prevented applications written for 1.6 using custom filters from being able to use the 1.8 library. There is now an H5Z_class1_t and H5Z_class2_t to enable compatibility. H5Zregister is *not* versioned, it determines which version of the struct has been passed in by the value of the first field (id or version, both are ints). Tested: jam, linew, smirom (h5committest), jam (--with-default-api-version=v16)
* [svn-r16792] Description:Mike McGreevy2009-04-201-4/+4
| | | | | | | | | | | | - Updated bin/reconfigure to use latest version of automake (1.10.2). Re-generated Makefile.in's by running bin/reconfigure. - Added libtool version numbers to c++, fortran, hl, hl c++, and hl fortran libraries. Tested: jam, liberty, smirom
* [svn-r16669] Corrected the urls for h5dump xml dtd and schemaAllen Byrne2009-04-031-4/+4
| | | | Tested: Fedora 10 gcc
* [svn-r16629] removed a h5dump test (array type) that has a different bogus ↵Pedro Vicente Nunes2009-03-302-11/+7
| | | | | | | | | output in frebsd (liberty) removed the call to the file generation in the test generation program removed the binary h5 and ddl from svn tested: linux
* [svn-r16620] commented a run that fails cross platforms (liberty, abe) ↵Pedro Vicente Nunes2009-03-261-1/+1
| | | | regarding a "double" print
* [svn-r16614] 3. #1501 (B1) tools bug if dataset is larger than ↵Pedro Vicente Nunes2009-03-252-0/+50
| | | | | | | | | | | | 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-r16561] Purpose:Mike McGreevy2009-03-101-3/+3
| | | | | | | | | | | | | | | | | | Bug Fix Description: Fixing BZ #1381. The --includedir=DIR configure option, which is used to specify the installation location of C header files, did not work correctly as the path was hard-coded in config/commence.am. I'm presuming this is because an older version of automake didn't know where to put c header files. In any case, removing this line now defaults the includedir to the same directory that it is currently hard-coded to, and also fixes the configure flag to allow customization of this value. Tested: jam, liberty
* [svn-r16560] Description:Quincey Koziol2009-03-101-2/+1
| | | | | | | | | | Remove another call to H5E_clear_stack() from within the library. Clean up lots of compiler warnings. Tested on: Mac OS X/32 10.5.6 (amazon) (followup on other platforms forthcoming)
* [svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a ↵Pedro Vicente Nunes2009-02-261-0/+1
| | | | | | | 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) the way h5ls prints types, it starts searching for NATIVE types first. One solution would be h5ls not to detect these native types, using for example the same print datatype function that h5dump does, that would make the output look the same on all platforms ("32-bit little-endian integer" would be printed instead). Drawback, this "native" information would not be available. Other solution is to have not one but 2 expected outputs and make the shell script detect the endianess and compare with one output or other tested: h5committest
* [svn-r16489] Fixed bug #1459 by eliminating the macro long_long and ↵Allen Byrne2009-02-182-15/+15
| | | | | | | | | | | replacing all instances with long long. Tested: h5comittest fedora 10 x64 Vista 32, VS2005, IVF101 XP32, Cygwin
* [svn-r16012] Bug fixPedro Vicente Nunes2008-10-311-5/+9
| | | | | | | When -b was requested and no -o (file name) binary output was made to stdout Had a check after command line parsing to verify if -o is present, otherwise exit Tested: windows, linux
* [svn-r15992] Merge with 1.8 rev 15973Pedro Vicente Nunes2008-10-291-1/+4
| | | | | make -b accept both MEMORY and NATIVE Tested: linux
* [svn-r15991] Merge with 1.8 rev 15969Pedro Vicente Nunes2008-10-292-49/+65
| | | | | | | | | | | | | | | Introduced a new feature in the tools library regarding command line parsing In the definition of arguments, an "*" means that the switch can or can not have an optional argument. This "*" is put in the code regarding the letter definition, and it is transparent to the user (e.g b* instead of the previous b: ), where ":" notes a required argument after the letter (and no ":" or "*" notes no argument, mandatory) Used for the h5dump binary option -b It can be now 1) -b (defaults to NATIVE) 2) - b NATIVE 3) - b FILE 4) -b LE 5) -b BE Note: the keyword NATIVE replaces MEMORY This feature (-b with no argument) was tested with the sequence of h5dump to binary (NATIVE) then h5import to generate an HDF5 file from the binary file and h5diff to compare the 2 HDF5 files Tested: linux
* [svn-r15942] Purpose: Bug Fixes and Libtool UpgradeMike McGreevy2008-10-241-6/+6
| | | | | | | | | | | | | | | | | | Description: - Remove need to set LD_LIBRARY_PATH when using shared szip library. - Libtool 2.2.6a is now used to generate libraries. - 'make check install' dependency bug is fixed, and should no longer break the build. - removed hard coding of shell in config/commence.am, as this causes problems on Solaris with the new version of libtool. - RELEASE.txt with appropriate changes. Tested: - kagiso, smirom, linew (merged from 1.8, pretty quick tests)
* [svn-r15886] Purpose: Close bug 1332Neil Fortner2008-10-163-72/+357
| | | | | | | | | Description: Improved external link traversal of h5dump. h5dump will now properly avoid all cycles, even those spanning multiple files. Improvement to the output of committed datatypes. Committed datatypes are now checked for uniqueness (like other objects). Tests added for these cases. Tested: kagiso, linew, smirom (h5committest)
* [svn-r15668] Purpose: Add feature requested in bug #1282Neil Fortner2008-09-211-1/+7
| | | | | | | | | | Description: Adds capability to h5ls to traverse external links when the -r (recursive) option is given. Changes to the way absolute path names are patched in h5trav.c. Changes to the way recursive traversal starting from a non-root group is handled (which also fixes some preexisting issues). Tests added for these cases. Tested: kagiso, smirom, linew (h5committest)
* [svn-r15628] Description:Quincey Koziol2008-09-163-314/+314
| | | | | | | | | | | | | Remove trailing whitespace from C/C++ source files, with the following script: foreach f (*.[ch] *.cpp) sed 's/[[:blank:]]*$//' $f > sed.out && mv sed.out $f end Tested on: Mac OS X/32 10.5.5 (amazon) No need for h5committest, just whitespace changes...
* [svn-r15462] Description:Quincey Koziol2008-08-121-1/+1
| | | | | | | | Correct compiler warnings from Visual Studio. Tested on: Mac OS X/32 10.5.4 (amazon) w/FORTRAN & C++ (Too minor to require full h5committest)
* [svn-r15446] bug fixPedro Vicente Nunes2008-08-071-1/+14
| | | | | | | http://bugzilla.hdfgroup.uiuc.edu/show_bug.cgi?id=788 don't print array indices for regions tested: windows, linux
* [svn-r15337] Unintended change to h5dump.c. Reverted.Neil Fortner2008-07-081-12/+8
|
* [svn-r15335] Fixed incorrect error message in H5Pset_fletcher32:Neil Fortner2008-07-081-8/+12
| | | | | | | | "unable to add deflate filter to pipeline" -> "unable to add fletcher32 filter to pipeline" Tested: kagiso
* [svn-r15183] Purpose: _WIN32 macro cleanupScott Wegner2008-06-091-4/+0
| | | | | | | | | | Description: As part of our Windows cleanup, we try to remove windows-specific tweaks in the source code. There are many instances where Windows code is introduces via ifdef's. We re-evaluate whether they are still required, and found that many of them are not. Others we change to "feature"-specific code, rather than Windows-specific. Tested: VS2005 on WinXP VS.NET on WinXP h5committest (kagisopp, smirom, linew)
* [svn-r15150] Purpose: Separate Windows function macro definitions to win32defs.hScott Wegner2008-06-051-1/+1
| | | | | | | | | | | | | | Description: In library code, we try not to use system calls directly, but instead use the HD{function} macro instead. This way, we can map special versions of the call on particular systems. Previously, it was all done in H5private.h. However, in an effort to clean up platform-specific definitions, we move all of the Windows macros into a separate file, win32defs.h. This way, we can use the non-Posix versions that Visual Studio sends warnings about. Some macros are set specifically in the platform-specific header files. Then, any macros left unset will be set by the "default" implementation in H5private.h. This checkin also cleans up various source files to use the HD* macros when possible. Tested: VS2005 on WinXP VS.NET on WinXP h5committest (kagiso, linew, smirom)
* [svn-r15143] Pedro Vicente Nunes2008-06-052-8/+16
| | | | | | | | | | Fix for #1169 http://bugzilla.hdfgroup.uiuc.edu/show_bug.cgi?id=1169 don't print attributes to stdout when doing binary output added an attribute to the file run on the binary output test tested: windows, linux
* [svn-r15036] Bug fix.Albert Cheng2008-05-191-4/+4
| | | | | | | | | | | | | | | | | | | Description: The fortran Makefile.am used HDF_FORTRAN to indicate it is part of the Fortran API source so that conclude.am will give fortran api prefix in the test output. The symbox HDF_FORTRAN is also used in configure for a different purpose (indicated --enable-fortran). They conflicted. Similar problem for the symbol HDF_CXX. Solution: Changed all the involved Makefile.am to use "FORTRAN_API" instead. It is a more appropriate name. Same for CXX_API. Along the way, discovered that the Makefile.am of hl/fortran/test and hl/cxx/test did not have those symbols at all. Added them in. Platform tested: Kagiso only. It is a trivia change.
* [svn-r15007] Purpose: configure cleanupMike McGreevy2008-05-151-1/+0
| | | | | | | Description: cleaning up configure related to removal of --disable-hsizet flag, which we no longer support. Tested: kagiso
* [svn-r15003] Purpose:Albert Cheng2008-05-151-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improvement. Description: src/libhdf5.settings was the initial configure summary and is installed. Then configure is changed to dump a summary of the configure settings to the output and also append it to src/libhdf5.settings. That created two different output formats and duplicated information. This is the initial attempt to clean up this confusion and unify the output format. It is decided to use the src/libhdf5.settings template as the unified means. This requires more macros symbols be defined. The following symbols are all related to generating the src/libhdf5.settings file. AC_SUBST(EXTERNAL_FILTERS) AC_SUBST(MPE) MPE=no AC_SUBST(STATIC_EXEC) STATIC_EXEC=no AC_SUBST(HDF_FORTRAN) HDF_FORTRAN=no AC_SUBST(FC) HDF_FORTRAN=no AC_SUBST(HDF_CXX) HDF_CXX=no AC_SUBST(CXX) HDF_CXX=no AC_SUBST(HDF5_HL) HDF5_HL=yes AC_SUBST(GPFS) GPFS=no AC_SUBST(LINUX_LFS) LINUX_LFS=no AC_SUBST(INSTRUMENT) INSTRUMENT=no AC_SUBST(CODESTACK) CODESTACK=no AC_SUBST(HAVE_DMALLOC) HAVE_DMALLOC=no AC_SUBST(DIRECT_VFD) DIRECT_VFD=no AC_SUBST(THREADSAFE) THREADSAFE=no AC_SUBST(STATIC_SHARED) AC_SUBST(enable_shared) AC_SUBST(enable_static) AC_SUBST(UNAME_INFO) UNAME_INFO=`uname -a` The src/libhdf5.settings.in has CONDITIONAL's added to it too. The untrue conditions turned into a "#" and these lines are cleaned by the post processing script. Platform tested: h5committest on kagiso, smirom and linew.
* [svn-r14977] update comments, formattingPedro Vicente Nunes2008-05-121-5/+9
| | | | tested: windows, linux
* [svn-r14976] Support for external links follow up. The format is to print ↵Pedro Vicente Nunes2008-05-122-32/+184
| | | | | | | | | | | | | | | | | | | | | | | | | | | | the target object as part of TARGETPATH, noted with some extra indentation The previous printing of LINKCLASS 64 was removed HDF5 "textlinksrc.h5" { GROUP "/" { EXTERNAL_LINK "ext_link1" { TARGETFILE "textlinktar.h5" TARGETPATH "dset" DATASET "dset" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 6 ) / ( 6 ) } DATA { (0): 1, 2, 3, 4, 5, 6 } } } } } There is no script test for this behavior so far, because test script uses complete paths that vary from test to test, making not possible to define a valid TARGETFILE in the file tested: windows, linux, solaris
* [svn-r14937] fix typo in commentPedro Vicente Nunes2008-05-061-2/+2
|
* [svn-r14935] correct an error in the usage textPedro Vicente Nunes2008-05-051-1/+1
| | | | tested: windows, linux, solaris
* [svn-r14934] Add a test for the floating point user defined printf formatPedro Vicente Nunes2008-05-053-3/+70
| | | | | | | | | | | | | | | | Usage is -m T, --format=T Where T - is a string containing the floating point format, e.g '%.3f' The test consists of writing a number with 7 fractional digits (default precision display of %f is 6 digits) and have the 7 digits displayed with -m %.7f fpformat.h5 Tested: windows, linux, solaris Note: the output file was generated in linux, it may be possible that platforms other than the ones tested have a different representation of the number
* [svn-r14933] Purpose: Updating HDF5 to use automake 1.10.1 and libtool 2.2.2Mike McGreevy2008-05-051-16/+20
| | | | | | | | | | | | | | | | | | Description: Applying update to autotools that was applied to 1.8 a couple of weeks ago to the trunk. Updated bin/reconfigure script to reflect the new versions of libtool and automake in the /home1/packages/ directory. Rearranged configure.in script. When using libtool 2.2.2, the libtool script doesn't generate until later in the configuration process, so I had to move a test that parsed through the libtool script to a point after where it was actually being generated. Ran libtoolize on the project, and ran bin/reconfigure to regenerate configure and Makefile.in's throughout. Tested: kagiso, smirom, linew (h5committest)
generated by cgit v0.12 at 2024-09-16 15:13:29 (GMT)