| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Initial checkin of extensible array data structure prototype code and
regression tests.
Initial definitions for revised FUNC_ENTER/LEAVE and error reporting
macros, which are being vetted in the extensible array code.
Minor warning and formatting cleanups in other sections of code.
Tested on:
Mac OS X/32 10.5.4 (amazon) in debug mode
Mac OS X/32 10.5.4 (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 (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
|
|
|
|
|
|
|
|
|
| |
Added files:
./fortran/src/H5_DBLE_InterfaceInclude.f90
./fortran/src/H5_DBLE_InterfaceExclude.f90
Contains the DOUBLE PRECSION interfaces depending on
the state of FORTRAN_DEFAULT_REALisDBLE_F.
|
|
|
|
|
|
|
|
| |
Description:
Add new Windows project files to MANIFEST
Tested:
none
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
reference count
> 1.
Description: Added a new field 'app_count' to H5I_id_info_t struct, to track
the reference count on an id due to the application. the old 'count' field
tracks the total. Generally any id visible to the application gets placed
in app_count. Added app_ref boolean parameter to H5I_inc_ref, H5I_dec_ref,
H5I_register, H5I_clear_type, and a few other functions, to specify whether
the operation(s) being performed on the id(s) are due to the application
(TRUE) or not (FALSE). Test added for this case.
Tested: kagiso, smirom, linew (h5committest)
|
| |
|
| |
|
|
|
|
| |
tested: windows, linux
|
|
|
|
| |
tested: linux
|
|
|
|
|
|
| |
hl/tools/gif2h5/testfiles
tested: linux
|
|
|
|
| |
tested: linux
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The name of the files are now given by its full name relative to $srcdir
To avoid the printing of the complete full path of the test file, that hides
all the other parameters for long paths, the printing of the command line
is done first in TESTING with the name only of the test file, not its full path
the printing in the expected output that had the file name was removed as well as 3 tests that tested error messages in which the file name was present
tested: linux (in 2 different build directories relative to $srcdir), solaris
|
|
|
|
|
|
| |
Moved all h5diff testfiles from /tools/testfiles to tools/h5diff/testfiles
Tested: linux, solaris
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Description:
To follow the naming convention for source files, we simply rename the new header to H5win32defs.h
Tested:
None, simple name change.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed bug in h5ls that prevented relative group listings (like
"h5ls foo.h5/bar") from working correctly.
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (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/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.5.3 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
Previously, we maintained some source files that are commonly generated dynamically on other systems. Now, we also generate them on Windows as well. We should remove them from the repository so old versions are not accidentally used.
Also, clean up the project files to organize generator programs.
Tested:
VS2005 on WinXP
VS2005 on WinXP x64
VS.NET on WinXP
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Description:
There were a number of small tweaks we needed to make to add the new fortran_1_8 code on Windows. We create new project files, add new source to them, add the test to our test suite, and fix a few typos in the Windows-specific source code.
Tested:
VS2005 on WinXP
|
| |
|
|
|
|
|
|
|
| |
branch back into the trunk (up to revision 14921)
Platforms tested: kagiso with g95 and Intel compilers; more testing will be done after checking in a fresh
copy from the trunk. New code itself was tested with all Fortran compilers available at THG
|
| |
|
|
|
|
| |
New fortran wrappers added.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Omnibus raw data I/O revisions, with wide-ranging changes and
refactoring, in order to prepare for implementing "fast append" feature.
These changes remove the majority of the code duplication for raw data
I/O which has crept in over the last ten years and introduces a more object-
oriented design for operating on different types of dataset storage.
Chunked storage no longer has it's own I/O routines, it is now handled
as either contiguous (if chunk is not pulled into the cache) or compact (if the
chunk is cached in memory).
No bug or feature changes, at least intentionally... :-)
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (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/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.5.2 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
|
|
|
|
|
|
|
|
|
|
| |
Description:
On Windows, many POSIX functions have been replaced by a similarly-named function with some additional security-checking. Visual Studio issues a warning each time the POSIX version is used, recommending that we replace it with the new version. This results in thousands of errors when building the HDF5 library.
This checkin adds a Visual Studio "Property Sheet", which has been applied to all library projects, and defines a number of preprocessors to suppress these warnings. The warnings have been disabled only in Visual Studio 2005 project files, as VS.NET doesn't support property sheets.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
Add ./windows/hdf5build_examples.BAT to MANIFEST
Tested:
chkmanifest on kagiso
|
|
|
|
|
|
|
|
| |
Description:
The ohdr_gentst project exists in order to re-create test input files that are distributed with the source. These projects aren't built by default on most platforms, and the source isn't distributed in release builds. To avoid confusion and bloat, we remove the Windows version of this project.
Tested:
None, only removed
|
| |
|
|
|
|
|
| |
Tested:
chkmanifest on smirom
|
| |
|
|
|
|
|
|
|
|
| |
Description:
Removed ./c++/examples/testexamples.sh
Platforms tested:
Not needed.
|
| |
|
|
|
|
|
|
|
|
|
| |
Description:
The Windows suite of examples for HL C was a very small subset of the examples that exist for other platforms. Now we have all of the HL C examples-- integrated into the VS projects files, and batch test scripts.
Tested:
VS2005 on WinXP
VNET on WinXP
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
platforms
Description:
The collection of HL C examples that we distribute for Windows is incomplete. I wasn't aware of it until Pedro pointed it out, because we use different (although similar) names for the generated files. This checkin changes the naming to follow Linux, in preparation to add the rest of the HL examples to Windows.
Note: I believe I've updated the MANIFEST accordingly, but I may have missed something-- I'll check on Linux shortly after this commit.
Tested:
VS2005 on WinXP
VS.NET on WinXP
|
|
|
|
|
|
| |
and agreed policy
see http://www.hdfgroup.uiuc.edu/RFC/HDF5/QA/RFC-HIS-REL-1.8_Feb6.pdf
|
|
|
|
|
| |
Details:
We no longer support Visual Studio 6.0, so we note it in the documentation. Also, updated the path references in VS.NET documentation
|
|
|
|
|
|
|
|
| |
Description:
Minor edit to MANIFEST, delete a few entries I missed last time. This brings it up to date.
Tested:
chkmanifest on smirom
|
|
|
|
|
| |
Description:
Update the MANIFEST for the files I've just addeed/removed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add work-around to allow reading files that were produced with a buggy
earlier version of the library, which could create objects with the wrong
object header message count. There is now a configure flag
"--enable-strict-format-checks" which triggers a failure on reading a file
with this sort of corruption (when enabled) and allows the object to be read
(when disabled). The default value for the "strict-format-checks" flag is
yes when the "debug" flag is enabled and no when the "debug" flag is disabled.
Note that if strict format checks are disabled (allowing objects with
this particular kind of corruption to be read) and the file is opened with
write access, the library will re-write the object header for the corrupt
object with the correct # of object header messages.
This closes bugzilla bug #1010.
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (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/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.4.10 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
|
|
|
|
|
|
|
|
|
| |
Updated utilities test scripts to make output more legible; fixed some typos.
Added four new expected output files to avoid false negative reports
for the h5dump tests (for ones that expect to have error report in them).
Updated MANIFEST to reflect the changes.
Platforms tested:
VMS server (more testing is on the way)
|
|
|
|
|
|
|
|
| |
Refactor file space allocation routines into separate source module.
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
Mac OS X/32 10.4.10 (amazon) in debug mode
|
|
|
|
|
|
|
|
| |
dataspace selection. Added a test
for it, too. This round of checkin isn't well tarnished yet. I'll come back to work on Jan. 8. I'll revise it then.
Tested it on kagiso, smirom, linew.
|
|
|
|
|
|
| |
removed obsolete command file
Platforms tested: VMS server
|