| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Make a copy of the index value for H5Giterate and use that instead of
dereferencing the index pointer.
Platforms tested:
FreeBSD 4.9 (sleipnir)
too minor to need h5committest
|
|
|
|
|
|
|
|
|
|
| |
feature
Description:
-setup now also sets up or updates the current source directory.
Platforms tested:
LANL Theta.
|
|
|
|
|
|
|
|
|
|
|
|
| |
directory. This eliminates the problem that the builder may not
have permission to install in the default install directory.
It also allows multiple builds in the same host or multiple srcdir
using the same source.
Platforms tested:
Eirene plus eyeballing of changes.
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Synchronized with the changed v1.7 branch. No content change,
purely just formatting.
Platforms tested:
Copper (pp).
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
| |
Added *.clog which are generated by the MPE option, to the CLEAN list.
Platforms tested:
Tested in copper which supports the MPE option.
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
new test.
Description:
Added test_mpio_1wMr test which verifies if the file system can support
the POSIX requirement of 1 process writes, many processes read.
This version also has the option of using atomicity and file-sync.
Platforms tested:
Tested only in Copper since this is particular to C parallel.
Misc. update:
Update release_docs/RELEASE.
|
|
|
|
|
|
|
| |
Bug fix
Description:
Correct typo in gcc 2.96 warning
|
|
|
|
|
|
|
|
|
|
|
|
| |
new feature
Description:
Folded the new feature of -setup option into this branch too.
Platforms tested:
Tested in LANL Theta.
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
| |
Code cleanup
Description:
Clean up a compiler warning
Platforms tested:
Titan (user02)
Too minor to require h5committest
|
|
|
|
|
|
|
|
|
|
|
| |
Add warning
Description:
Warn users about known bugs for gcc 2.96
Platforms tested:
Titan (user02)
Does not apply to h5committest
|
|
|
|
|
|
|
|
| |
Update ecc compiler flags
Platforms tested:
Titan
Not relevant to other platforms, so no h5committest.
|
|
|
|
|
|
|
|
|
|
|
| |
Small bug fix
Description:
MPI_DOUBLE_PRECISION -> MPI_DOUBLE in C code.
Platforms tested:
Cray T3E (hubble)
Too minor to require h5committest
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Handle denormalized floating-point values in a more general way that
uses a different 'epsilon' for determining if two values are "close enough"
Platforms tested:
FreeBSD 4.9 (sleipnir)
h5committest
Pittsburgh Alpha Cluster (lemieux.psc.edu)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update DEC compiler support
Description:
Updated DEC/Compaq compiler detection to handle DEC->Compaq switchover
in compiler version string.
Also, copied v5.x compiler flags to V6.x compiler flags and included the
-ieee and -misalign flags necessary for correct floating-point support.
Platforms tested:
Pittsburgh Alpha Cluster (lemieux.psc.edu)
|
|
|
|
| |
Update release notes with recent bug fix.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Omnibus floating-point bug fix changes
Description:
There are a number of problems in the floating-point conversion code that
were exposed by Ray's recent int<->float checkin:
- The 'my_isnan' code in test/dtypes.c was broken and would always return
true. The meant that the actual values in the float<->float conversion
tests were _never_ checked, hiding the other bugs included in this
checkin.
- A recent change I made to the type conversion code used "FLT_MIN" instead
of "-FLT_MAX" for the most negative 'float' value for the double->float
conversion, which meant that any the negative number that was converted
from a double to a float would have been mapped to zero, essentially.
- A change that Robb appeared to have made ~2.5 years ago to the "generic"
float->float conversion routine appears to be incorrect and I've backed
it out.
- Floating-point conversions on SGI's which converted denormalized values
would be mapped to zero instead of being propertly preserved in the new
type. This was addressed by an SGI-specific system call to prevent the
behavior.
Solution:
Described above, generally.
Platforms tested:
FreeBSD 4.9 (sleipnir)
h5committest
Misc. update:
release_docs/RELEASE update forthcoming...
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Remove release number from document title
Description:
Removed "Release 1.4" from "Introduction to HDF5" document title.
Platforms tested:
IE 5
|
|
|
|
| |
Mention metadata benchmark in release notes.
|
|
|
|
|
|
|
|
|
|
|
| |
Add metadata benchmark to the 1.6 branch
Description:
Port the metadata benchmark to the 1.6 branch, for LANL's use (mostly).
Platforms tested:
FreeBSD 4.9 (sleipnir) w/parallel
not tested with h5comittest, so it wasn't run
|
|
|
|
| |
Update release notes with metadata change information
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Our previous "optimization" of metadata writing which only wrote metadata
from one process was abusing MPI-I/O and after some consultation with Rob Ross
and Rajeev Thakur, Albert & I have come up with a solution...
Solution:
Instead of only writing from one process, issue a collective write
operation with all processes, for metadata writes.
Platforms tested:
FreeBSD 4.9 (sleipnir)
h5committest
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bug fix
Description:
If using g++ on HP-UX, the flags for aCC would be placed on the
command line. This was causing g++ to fail the configuration test.
Solution:
CHanged the test so that it's a case statement. If it's the aCC
compiler, then use those flags. Otherwise, don't specify flags. This
case statement can be modified to provide compiler-specific flags in
a similar way to other config/* files.
Platforms tested:
Hp-UX (Hp-UX specific change.)
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
CFLAGS wasn't using user-set values in one instance
Solution:
Changed CFLAGS="..." to CFLAGS="$CFLAGS ..."
Platforms tested:
Arabica
(the machines affected)
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
CXXFLAGS and CPPFLAGS wasn't including user-set values.
Solution:
Changed CXXFLAGS="..." to CXXFLAGS="$CXXFLAGS ..." and CPPFLAGS="..."
to CPPFLAGS="$CPPFLAGS ..."
Platforms tested:
Kelgia,
Modi4
Arabica
(the machines affected)
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Buglet Fix
Description:
The FFLAGS environment variable wasn't being passed to the Makefiles.
The config files weren't including it when they set the FFLAGS
variable.
Solution:
Changed the FFLAGS="..." command to FFLAGS="$FFLAGS ..." instead.
Platforms tested:
Copper
Arabica
Verbena
Misc. update:
|
|
|
|
| |
Update manifest with new files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix.
Description:
The new routines added for H5MM_[m|c]alloc were causing the function
stack code to infinitely recurse while allocating room for the thread-specific
information (when thread-safety was turned on).
Solution:
Call HDmalloc directly instead of H5MM_malloc
Platforms tested:
FreeBSD 4.9 (sleipnir)
Changed are not tested in h5committest
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Variable length strings and sequences with NULL pointers were not handled
by library, causing problems access the data. This also affected fill values
for variable-length datatypes.
Solution:
Address the issues in the library by detecting NULL sequences/strings
and avoid trying to convert them.
Patched up dumper to display NULL sequences/strings.
Platforms tested:
FreeBSD 4.9 (sleipnir)
h5committest
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix.
Description:
Skip over situation where malloc(0) might occur.
Platforms tested:
IBM p690 (copper)
too minor to require h5committest
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix & code cleanup
Description:
Allowing the library to call malloc with a size of 0 bytes causes problems
for some users, so we check for allocations of 0 bytes and disallow them now.
Cleaned up some code which could call malloc with 0 size.
Changed some code calling HDmalloc directly to call H5MM_malloc(), which
allows us to check for 0 sized allocations.
Platforms tested:
FreeBSD 4.9 (sleipnir)
too minor to require h5committest
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Make --disable-hsizet work properly again by fixing a couple of tests and
correcting the definition of SSIZET_MAX.
Platforms tested:
FreeBSD 4.9 (sleipnir)
h5committest not used, as it doesn't test this configuration.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code optimization
Description:
Improved integer & floating-point datatype conversions by removing some
corner cases. Got rid of algorithm which walked the buffer of elements to
convert backwards, switching to algorithm which computes the non-overlapping
space in the buffer and repeatedly converts it in the forward direction.
Platforms tested:
FreeBSD 4.9 (sleipnir)
h5committest
Cray SV1 & T3E (T90 is not accessible)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Don't check the number of szip parameters set during the "can apply" and
"set local" callbacks, be safe about setting the parameters instead.
Platforms tested:
FreeBSD 4.9 (sleipnir)
too minor to require h5committest
|
|
|
|
|
|
|
|
|
|
|
| |
Warning cleanup
Description:
Make a parameter 'const' to clean up a warning during compiles.
Platforms tested:
FreeBSD 4.9 (sleipnir)
too minor to require h5committest
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bug fix.
Description:
It sometimes complained of wrong number of argument to test.
This happened when more than 1 tool are redeployed.
The problem is due to an unquoted variable expanded into
multiple strings, confusing the test command.
Fixed by putting quotes around it.
Platforms tested:
only tested in verbena since it is trivial.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Improved tools index
Better categorization and consistency in style
Clarified notes regarding tools that are not included with the
library distribution
Added notes in the h4toh5 and h5toh4 descriptions that these tools
are now distributed separately (with pointer to distribution site)
A few dozen copy edits
Platforms tested:
IE 5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code cleanup & simplification
Description:
Replace [non-working] code in routine to build up an MPI derived type for
a hyperslab selection that was supposed to "flatten" out contigous blocks with
code that uses a selection iterator (which _does_ have working "flattening"
code).
Remove "contiguous hyperslab" code for MPI selections as it is unnessary
now.
Platforms tested:
FreeBSD 4.9 (sleipnir) w & w/o parallel
Linux 2.4 (verbena) w/FORTRAN & C++
Solaris 2.7 (arabica) w/64-bit
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix & code cleanups
Description:
Change our use of MPI derived datatypes to not create datatypes with
"0-sized" lengths, which causes the LANL Q machine to hang.
Also, get rid of "prefer MPI derived datatypes" environment variable since
it has no advantage.
Platforms tested:
FreeBSD 4.9 (sleipnir) w & w/o parallel
h5committest
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Fixes for user-reported Ref Manual bugs:
H5Gget_objname_by_idx: corrected 'size' parameter specification
H5Sselect_elements: Expanded 'coord' parameter description to make it
clear that values are 0-based.
Additional minor copy edits and formatting cleanup.
Platforms tested:
IE 5
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"bug fix", sort of.
Description:
now that stream-vfd is on by default, it does not work for Tflops.
Set it to no by default.
Platforms tested:
Tested in Tflops.
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update
Description:
Added check for correctly working basename and xargs programs. Mike
McKay was having problems with broken xargs. The basename check was
just a good idea.
Platforms tested:
Linux & Arabica (trivial change already done in mainline branch).
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code cleanup
Description:
Untwist the last few sections of code before starting on fixing the
problems with reading off the end of the file in earnest.
Platforms tested:
FreeBSD 4.9 (sleipnir)
FreeBSD 4.9 (sleipnir) w/parallel
h5committest not necessary - parallel only changes
|