| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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:
A small typo in the main Windows test script was causing the C++ library tests not to run by default.
Tested:
VS2005 on WinXP x64
|
|
|
|
|
|
|
|
| |
Description:
When building HDF5 with thread safety on Windows, the err_compat test was failing because our output was being parsed incorrectly. Rather than having a thread number in the error stack trace, there will be the string "some thread: no way to know the thread (IDs): from pthread on windows:". This checkin now takes this into account, and modifies the output accordingly.
Tested:
VS2005 on WinXP with Pthreads
|
|
|
|
|
|
|
|
|
|
| |
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:
Vailin has been working on some new tests for converting Windows paths. She found a bug that is making these two tests fail, but didn't have time to fix it. We've commented out the two tests until she has time to fix the bug. This won't affect other platforms because it's Windows-specific code.
Tested:
VS2005 on WinXP
|
|
|
|
|
| |
Description:
Added notes about fixes on bugzillas 1045 and 1056.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
- Revised Attribute::write and Attribute::read wrappers to handle
memory allocation/deallocation properly. (bugzilla 1045)
- Changed free() to H5Dfree(), also needed H5private.h
- Corrected quite a few typos in documenting!
Platforms tested:
SunOS 5.10 (linew)
Linux 2.6 (kagiso)
FreeBSD (duty) - there was something wrong in the C tests for makecheck
hung quite a long time; I went ahead with makecheck just in c++ dir,
since the changes didn't effect the C tests. I'll keep an eye on
the tests tonight...
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
remove HDputenv() from external_link_env() test
(will add script later to set HDF5_EXT_PREFIX for running the test)
modify and add more comments
2. src/H5private.h: remove #define for HDputenv()
Tested on kagiso, linew and smirom.
|
|
|
|
|
|
|
|
| |
Description:
Add ./windows/hdf5build_examples.BAT to MANIFEST
Tested:
chkmanifest on kagiso
|
|
|
|
|
|
|
|
|
|
| |
Description:
Just as we have scripts for building and testing the HDF5 library on Windows, hdf5build_examples.BAT is a new script for building HDF5 example projects on Windows. This is especially useful for our new Windows Daily Tests, to test our examples automatically as well.
Eventually, we will have hdf5check_examples.BAT and hdf5bt_examples.BAT to test our examples as well.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
|
|
| |
Description:
Previously, our Windows projects for HL Fortran examples were using outdated library names for our cstub code. As a result, they wouldn't build correctly. This checkin brings them up-to-date.
Also, add hdf5_hl.lib as a dependency to hdf5_hl_fortran.lib. This goes un-noticed when building the complete VS solution, but should be required when only building hdf5_hl_fortran.lib
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
|
|
| |
Description:
In the Windows Fortran example projects, the runtime library used for linking static-debug version was set incorrectly. This was a result of the project being upgraded from VS6 where we used Single-threaded libraries. Those libraries are no longer supported, so we use [Debug] Multithreaded [DLL] now instead.
Note that this also needs to be updated in the VS.NET project files-- I will make those changes shortly.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
Many new path-specific tests have been added via the "links" test. Because Windows' path format is non-standard, we need a special macro defined to handle it specially. Note that 2 tests still fail with this macro defined, but it should be fixed soon.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
In previous versions of Windows, the builtin 'FC' command (diff equivalent) didn't return proper exit status. As a work-around, we parsed the message returned to check status. This relies on English return messages.
In current Windows XP and Windows Vista, FC will return exit status as expected, so we can remove this workaround. Older platforms where we would need this workaround are no longer supported.
Tested:
VS2005 on Windows XP
Small test on Windows Vista
|
| |
|
|
|
|
| |
Tested on kagiso, smirom, linew, and tg-login.
|
|
|
|
| |
Tested on kagiso, smirom, and linew.
|
| |
|
|
|
|
|
|
| |
tool.
Tested on kagiso, smirom, and linew.
|
|
|
|
| |
Tested on kagiso, smirom, and linew.
|
|
|
|
| |
Tested on kagiso, smirom, and linew.
|
|
|
|
| |
2. test/links.c: fixed one external link test to be the same as in 1.8.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
H5_DLL herr_t H5_build_extpath(const char *, char **/*out*/);
makes this stupid warning in windows that gets repeated in every source file
c:\_pvn\hdf5\src\h5private.h(958) : warning C4138: '*/' found outside of comment
changed signature to
H5_DLL herr_t H5_build_extpath(const char *, char ** /*out*/ );
compiler is happy now
tested: windows, linux
|
|
|
|
|
| |
Tested:
chkmanifest on smirom
|
| |
|
|
|
|
|
|
|
|
|
| |
Description:
A new source file has been added, ./test/chunk_info.c. As a result, we need to add new projects for Windows. This includes projects for VS2005 on VNET.
Tested:
VS2005 on WinXP
VNET on WinXP
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
a 4X4 dataset by iterating by 2X2 chunks
tested: windows
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The development branch was changed to default enable-production for the
v1.8 release but had not switched back to default development mode.
Solution:
Changed it back to --disable-production (aka development) as the default.
Also ran bin/reconfigure to update configure.
Tested:
Smirom only. No h5committest since the change is trivial and if it works
at smirom, it should work everywhere else.
|
| |
|
| |
|
|
|
|
|
|
| |
at the moment, the test is just a skeleton for future add ins
tested: windows
|
| |
|
| |
|
|
|
|
| |
(solaris did not support setenv() and unsetenv())
|
|
|
|
|
|
| |
after the first one. One variable that controls the binary output was incorrectly reset to zero after a binary output was done a first time. The effect was that on cases of several datasets, the ones after the first were not binary written. Eliminated the resetting of that variable and tested a file with several datasets. Modified the test file so that it is easier to test with the tool binread, that reads the binary output of h5dump.
tested: windows, linux
|
|
|
|
|
|
|
| |
1. src/H5F.c, src/H5system.c: formulate path for mainfile
2. src/H5Lexternal.c: add search for target file
3. configure.in: add H5_HAVE_WINDOW_PATH
4. test/links.c: add tests for external link
|
| |
|
|
|
|
|
|
|
|
|
|
| |
project
Description:
As pointed out by a user, we added an un-needed link directory for szip which is machine-dependent and, in his case, problematic. We can safely remove this reference because we already include the szip link directory elsewhere.
Tested:
None, simply removed
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Bring r14737 back from the 1.8 branch: Fix bug which would
incorrectly encode the member offsets for compound datatypes whose size was
between 256 & 511 bytes, when the "use the latest format" feature was enabled.
Tested on:
Mac OS X/32 10.5.2 (amazon) w/debug
FreeBSD/32 6.2 (duty) w/production
|
|
|
|
|
| |
formatted code
tested: windows, linux
|
|
|
|
|
|
| |
formatted code
bug fix: the 1.6 branch did not have a test for the existence of long double type on print_type (print name of datatype)
tested: windows, linux
|
|
|
|
| |
Tested: windows, linux
|
|
|
|
| |
Tested: windows, linux
|