H5Pset_istore_k() will validate the "ik" value to not exceed the max v1 btree entries (2 bytes)
The same check for H5Pset_sym_k() "ik" value.
h5committested.
Bring r26258 from the autotools_rework branch to the trunk - remove
the LDOUBLE_TO_INTEGER_WORKS macro/define, which was addressing issues with
SGI systems that are no longer supported.
Tested on:
Linux 2.6.x (jam) w/serial & parallel
Daily tested on branch for >2 weeks
Bring r26257 from autotools_rework branch back to the trunk - removes
the LDOUBLE_TO_INTEGER_ACCURATE macro/define, which was addressing problems
with SGI systems and is no longer supported.
Tested on:
Linux 2.6.x/32 (jam) w/serial & parallel
Daily tested on branch for >2 weeks.
h5pget_class_f should return hid_t for classtype
Also removed all left over C comment artifacts /* and */ in the Fortran comments.
Tested: h5committest
Also removed disabling shared when building Fortran on the Mac.
These fixes should fix all the building shared with Fortran problems. HDF5-247
Also fixes array bounds starting from zero in H5Pff.f90 routines.
Tested: h5committest
Description:
The following two constructors of classes: AbstractDs, IdComponent,
H5Location, and H5Object are no longer appropriate after the data member
"id" had been moved from IdComponent to the sub-classes.
The copy constructors are noop and will be generated by the compilers if
needed so they can be removed in 1.8.15 without effecting applications. The
other constructors will be removed from 1.10 release, and then from 1.8 if
their removal does not raise any problems in at least two 1.10 releases.
<Classname>(const hid_t h5_id);
<Classname>(const <Classname>& original);
Deprecation warnings are added to each of these classes.
The other classes are changed to call the default constructor instead of
one of the constructors above.
Platforms tested:
Linux/64 (platypus)
Linux/32 2.6 (jam)
SunOS 5.11 (emu)
Description:
Fixed base classes that were in wrong order on the prototype lines and
some misc. warnings.
Platforms tested:
Linux/64 (platypus)
Linux/32 2.6 (jam)
SunOS 5.11 (emu)
Description:
Parameter had the same name as the class' member's. Replaced parameter
with a different name.
Platforms tested:
Linux/64 (platypus)
Linux/32 2.6 (jam)
SunOS 5.11 (emu)
Description:
Missing initializing one of the base classes in multiple inheritance.
Added CommonFG() to constructors' prototype.
Platforms tested:
Linux/64 (platypus)
Linux/32 2.6 (jam)
SunOS 5.11 (emu)
Various tweaks for autotools thread-safety and Pthreads support.
- Moved the check for pthread_attr_setscope() into the thread-safe
checks section. Documented its necessity and added a cross-compiling
option and helpful comment.
- Moved the high-level library checks up to the same place where
Fortran and C++ are checked. This will make it easier to handle
threadsafe/high-level combinations later.
- Also changed the default of --enable-pthread to 'check', which is
the same as the old 'yes' behavior where we just check the standard
locations. 'yes' and 'no' are still accepted, though 'no' will
currently produce an error since the autotools only support Pthreads.
Fixes: HDFFV-9087
Tested on: h5committest
jam (w/ threadsafe)
Solaris and OS X.
Added public API functions that expose the C library's memory allocator
for use in filter functions that need to allocate or resize buffers.
Intended for use with filter plugins, particularly on Windows, where C
runtime (CRT) issues can cause problems.
Fixes: HDFFV-9100
Tested on: h5committest + OS X (quail) + Solaris (emu)
Purpose:
Fix HDFFV-9124 - Remove old libtool post-processing
Description:
This revision removes some post-processing of the generated libtool
script, which was added back in 2003 (see svn revisions 6285 and 6293)
to address a deficiency in which the script failed to set the '$wl'
variable for icc and pgcc compilers. Libtool has since fixed the issue,
and the post-processing we've been running has essentially been a no-op
for years, so it's safe for us to remove the post-processing snippet.
Tested:
Jam using pgcc and icc compilers.
H5Rdereference should check for default (HADDR_UNDEF) value and not continue processing and return so that ret value can be checked and handled properly
Tested: jam (gnu)
