| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Description:
A typo in the project output file name was causing Intel Fortran 10.1 to crash. The output file was set to "$(OutDir)\hdf5_fortranddll.dll " (three trailing spaces). IVF 9.1 ignored this error and continued gracefully. However, IVF 10.1 would simply crash. With this fix, we can now build on IVF 10.1 (so far..)
Tested:
VS2008 w/ IVF 10.1 on WinXP
|
|
|
|
|
|
|
| |
other minor cleanup in fillval.c.
Tested: kagiso
Same fix in trunk: kagiso (parallel), smirom, linew
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
The fillval test uses random input to test various fill cases. Certain boundary cases cause the test to fail, which produces sporadic errors on Windows. There is a bug filed for the issue here:
http://bugzilla.hdfgroup.uiuc.edu/show_bug.cgi?id=1155
We will disable the test until the bug is fixed.
Tested:
None, simply disabled.
|
|
|
|
|
| |
Added the function h5tget_native_type and associated
requirements.
|
|
|
|
|
|
|
|
| |
Description:
Somehow, the ttsafedll project was setup to build by default in Visual Studio .NET project files. This causes build errors when the HDF5_EXT_PTHREAD variable isn't defined or the pthreads library path isn't setup. It should be disabled by default.
Tested:
VS.NET on WinXP
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
On Windows, certain users were having trouble with the "ohdr" test, which does some processing on object header messages. The errors were hard to reproduce on our machines, and we eventually determined that the errors were timezone-specific.
The bug is triggered on Windows when processing timestamps very near the "Epoch" (midnight on 1/1/1970)-- the mktime() function does some automatic adjustment on the time to correct for timezones. In the USA, the correction adds a few hours; in Europe, it subtracts, thus giving us times pre-Epoch.
This only affects Windows because the Windows mktime() function cannot handle times before 1970-- other systems seemingly can.
The fix is to simply create timestamps only as early as 01/02/1970. This way, any timezone adjustment will still be post-Epoch.
This bug only affects the ohdr test, and shouldn't be a problem in the library. The earliest timestamps that will actually be read will be around the time HDF5 was created (~1996-7, per Quincey).
Tested:
(tested in trunk)
VS2005 on WinXP
h5committest (kagiso, linew, smirom)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bring back revision 15227 from trunk:
Small cleanups to copying datatypes
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
|
|
|
|
|
|
|
| |
Fix gcc 4.2 flag that was put in gcc 4.1 section
Tested on:
Eyeballed & man pages
|
|
|
|
|
|
|
|
|
|
|
| |
Bring back revision 15211 from trunk:
Update the gcc flags for version 4.3
Clean up warnings
Tested on:
Mac OS X/32 10.5.3 (amazon)
|
|
|
|
|
|
|
|
|
|
|
| |
Bring back revision 15208 from trunk:
Add a "HDcompile_assert" macro for assertions that can/should be checked
at compile time, as opposed to run time. (And used it for a couple of simple
cases, to begin)
Tested on:
Mac OS X/32 10.5.3 (amazon)
|
|
|
|
|
|
|
|
|
|
| |
Bring revision 15188 back from trunk:
Avoid leaking memory when copying the internal "shared" struct for
a named datatype when it's already been opened earlier.
Tested on:
Linux/64 2.6 (chicago)
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
|
|
|
|
|
| |
Description:
On Windows, the pthread_self function cannot be used to print the returned thread ID for debugging. Instead, we need a separate function, GetCurrentThreadId. To eliminate some Windows ifdef's in the code, we create two new function macros which can be used by all platforms. It is conditionally defined in H5win32defs.h, and globally in H5private.h.
Tested:
VS2005 w/ pthreads on WinXP
kagiso w/ pthreads
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
| |
- h5dump: when doing binary output (-b), the stdout printing of attributes
was done incorrectly. Removed printing of attributes when doing binary
output. PVN - 2008/06/05
|
|
|
|
|
|
|
|
|
|
| |
dependencies to all_fortran
Description:
The projects testhdf5_1_8fortran[dll] which test the new fortran features in HDF5 1.8 were not registered as dependencies to the "all_fortran" pseudo-project. As a result, the projects would not be built if you simply build all_fortran in Visual Studio, rather than "Build Solution". This is a very minor cleanup, but is neccessary to be consistent in our projects.
Tested:
VS2005 on WinXP x64
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bring back revision 15146 from the trunk:
Correct the definition of the 'nbytes' variable in the in-memory version
of the B-tree key for chunks from 'size_t' to 'uint32_t', to match the
definitions everywhere else.
Tested on:
Mac OS X/32 10.5.3 (amazon) debug & production
Linux/64 2.6 (chicago) production
|
|
|
|
|
|
|
|
| |
Description: Changing h5perf installation so only h5perf is installed when
parallel is enabled, while only h5perf_serial is installed when
parallel is disabled.
Tested: kagiso
|
|
|
|
|
|
|
|
| |
Description:
A new test case was added to the general testh5ls script. This update adds the test to Windows as well.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bug fixes.
Description:
Added code to create an empty hdf5 (named h5diff_empty.h5) in order to test
if h5diff compares correctly an empty hdf5 vs. a non-empty one.
Tested:
Tested in kagiso of h5diffgentest itself.
Verified by h5dump that h5diff_empty.h5 was indeed empty.
Then "h5diff h5diff_empty.h5 h5diff_basic1.h5" returned 0 (should have
returned non-zero).
|
|
|
|
|
|
|
|
|
|
| |
Brought revision 15133 back from trunk:
Fixed bug in h5ls that prevented relative group listings (like
"h5ls foo.h5/bar") from working correctly.
Tested on:
Mac OS X/32 10.5.3 (amazon)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bring back revision 15131 from trunk:
Finish omnibus chunked dataset I/O refactoring, to separate general
actions on chunked datasets from actions that are specific to using the v1
B-tree index.
Cleaned up a few bugs and added some additional tests also.
Tested on:
Mac OS X/32 10.5.3 (amazon)
Linux/32 2.4 (chicago)
|
|
|
|
| |
Tested on smirom.
|
|
|
|
|
|
|
|
|
|
| |
Description:
On Linux-like systems, we can get the ID of the current thread through a pthread_self. However on Windows, the return cannot be cast as a threadID, so we simply couldn't get the ID. Previously we simply gave up and printed a message that we couldn't get an ID. Instead, though, we can use the Windows-specific call to GetCurrentThreadId(), which achieves the same goal. This way we can provide better debug output with threadsafe features.
Tested:
VS2005 on WinXP
VS.NET on WinXP
(other platforms not tested because change is within _WIN32 ifdef)
|
|
|
|
|
|
|
|
|
|
|
|
| |
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:
In our Windows command-line build script, we now support building with Visual Studio .NET, although VS2005 is still the default. Building with VS.NET still imposes the same feature restrictions as through the IDE:
-- 64-bit builds are unsupported
-- Fortran is unsupported
Tested:
VS.NET on WinXP
VS2005 on WinXP
|
|
|
|
|
|
|
|
|
|
| |
Studio 2005
Description:
On Windows, we receive many compiler warnings because Microsoft has implemented many "security-enhanced" versions of POSIX functions. However, the old versions still exist, so the warnings can be ignored. By setting a preprocessor definition, we can disable many of these warnings. On a typical HDF5 build, this reduces the number of warnings from ~1500 to ~600
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ignored system library, standardize program debug information, and unify Windows h5tinit
Description:
These changes are made via a user's suggestion, bugzilla bug #1164. These have all been tested in the trunk, and are stable/favorable changes.
In many of our project files on Windows, we have our linker setting set to ignore old link libraries-- either libc.lib or libcd.lib. This is a relic from converting project files from old versions of Visual Studio to newer ones, and is unnecessary. We remove the ignored library from the project files. This actually makes no difference in the output binaries.
In our debug project configurations, many of the projects were generating debug information for "Program Database and Edit & Continue". Other projects were using different settings, or none at all. We standardize to use "Program Database" setting, because it generates much smaller .obj files and cuts out unnecessary debug information.
Previously, there was Windows-dependent code inside H5detect.c, because not all projects could access the gethostname() function. However, we standardize our project-files to link with WS2_32.lib, so now this function is available. Thus, the Windows-specific code has been removed from H5detect.c.
Tested:
VS2005 on WinXP
VS.NET on WinXP
|
|
|
|
|
|
|
|
|
|
| |
Description: While '-Wl,-rpath' information was being removed from compile
lines when using --disable-sharedlib-rpath, some information
was still hidden in another variable that never got reset and
thus snuck into the executables. This fix should take care of
that issue.
Tested: kagiso, smirom
|
|
|
|
|
|
|
|
| |
Description:
Shortly before the release, we noticed that one of our h5dump xml Windows tests failed when used with a release tarball. This is because of the Unix-style EOL characters in the expected output. For the release, we simply skipped the test. However, we can instead convert the expected output to Windows EOL format, and run the test. This is a backport from the HDF5 trunk.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
| |
HISTORY-1_8.txt and RELEASE.txt
for the further development in the branch.
|
|
|
|
| |
a new source tar ball.
|
|
|
|
|
|
| |
under /mnt/scr1/release-binary/hdf5/v181)
Checking in updated files before tagging the release.
|
| |
|
|
|
|
|
|
|
|
|
| |
Description:
Noted the change from:
void IdComponent::dereference(IdComponent& obj, void* ref)
to
void H5Object::dereference(H5File& h5file, void* ref)
void H5Object::dereference(H5Object& obj, void* ref)
|
|
|
|
| |
of v1.8.1.
|
|
|
|
|
|
|
| |
Added and updated instructions for Red Storm serial and parallel build.
RELEASE.txt:
Added Red Storm information. Also, rearranged order of entries according
to more recent first.
|
|
|
|
|
|
| |
(should be done long time ago ;-) before
rolling the 1.8.1 release tar ball.
|
|
|
|
|
| |
Description:
Added notes about fixes of bugzillas 1045 and 1068.
|
|
|
|
| |
Editorial pass
|
|
|
|
|
|
|
|
| |
Description:
On test fails from the release tarball. Specifically, the h5diff xml test for tsaf.h5.xml. For some reason, fc (Windows diff utility) detects differences from the expected output if the file has unix-style end-of-line characters. It only happens for this test. I suspect it is because the file is so long, but it's too late to debug for the release. Simply comment it out until we can fix it.
Tested:
VS2005 on WinXP (32- and 64-bit)
|
|
|
|
| |
Summary sections for THG and NCSA machines.
|
|
|
|
|
|
| |
release. There is still work to do
on this file before the source release.
|
|
|
|
|
|
| |
1.8.1-rc1 before creating a tar
ball for remote testing
|
|
|
|
| |
Added processor id in failure messages for MPI.
|
|
|
|
|
|
|
|
|
| |
Removed extra MPI calls in subroutine by just passing
MPI variables into subroutines.
Added checks for MPI errors.
Cleaned-up formatting.
|
|
|
|
|
|
| |
memory growth; fixed
Platforms tested: kagiso (minor fix)
|
|
|
|
|
|
|
|
|
|
| |
Description:
Removed an unnecessary member function, H5File::dereference.
Platforms tested:
SunOS 5.10 (linew)
Linux 2.6 (kagiso)
FreeBSD (duty)
|