symbols, asserts, profiling, and optimization.
Also much refactoring, improved help, and --enable-<foo> options will
now emit errors on nonsense (e.g.: --enable-foo="asdfasdf").
The libhdf5.settings.in file was also reformatted.
Tested on: 64-bit Ubuntu 15.10 (Linux 4.2.0 x86_64) gcc 5.2.1
serial and parallel autotools w/ various options
For make installcheck, compile and run installed examples using the installed scripts. They were being compiled but not run.
Add Fortran2003 examples to the run-ex-fortran script when fortran2003 is enabled.
Set flag to -O3 in production mode for Intel compilers other than those with specified other settings.
Gentoo patches:
Remove unnecessary setting of LD_LIBRARY_PATH from configure.
Prevent potential array subscript out of bounds error in perform/pio_engine.c and sio_engine.c.
Tested with h5committest on jam, koala, ostrich and platypus, on emu and kite, and parallel tests on jam, koala and platypus with mpich built with gnu 4.8.2 and with intel compilers.
unknown versions of the C Intel compilers.
Modified apple config file to display Intel compiler information.
Updated RELEASE.txt notes accordingly.
Platfroms tested: jam, amani and dubna (Mac 64-bit) with Intel C, Fortran and C++ compilers.
Bump optimization down for Intel 10.* compilers, due to apparent bad cod
e generation.
Tested on:
Linux/64 2.6 (cobalt) w/debug & production & Intel 11.1 compilers
(h5committest not appropriate)
with Intel 10.0 compiler.
Solution: Use -O1 optimization flag with Intel 10.0
Platforms tested: abe and kagiso with Intel 10.0 and Intel 9.1 compilers; no committest
is needed since this is a compiler specific change.
-O3 flag causes compilation problems on most of the platforms with Intel compiler.
The problem exists in all vesrions of icc compiler up to the newest 9.1
Solution:
Use less agressive default setting O2 to avoid headache
Platforms tested: Linux 2.6 ia64 at UCAR (hal), cobalt (NCSA)
H5_CFLAGS change
Description:
Converted a few platforms to use H5_CFLAGS to "test the waters"
Solution:
Modified a few config/* files to use H5_CFLAGS for non-essential
flags.
Platforms tested:
mir, heping
Description:
Add source code copyright notice; comment symbols vary by type of file.
Platforms tested:
No changes that should cause any problems. Nonetheless, the tree will
be checked out fresh and tests run immediately post-commit.
mpich 1.2.6 does not like the tweaking of using -O2 flag.
Comment out the Tweaking since it caused problems to mpich1.2.6.
Need to investigate the reasons and effects to tweak.
Platforms tested:
Tested in heping using mpich 1.2.6 and in eirene uisng mpich 1.2.6.
Improvement
Description:
Added strip option to PROD_CFLAGS to remove symbols for smaller
production file size.
Solution:
Platforms tested:
Misc. update:
Bug fix.
Description:
Last commit would impose $arch even if user has provided his own
$CFLAGS. Fixed it.
Removed the wording of gnu-flags inherited from the copy.
Platforms tested:
Tested in tg-ncsa.
Misc. update:
Bug fix.
Description:
Restored correct setting of compilers (-Wall etc for debug flags
only, c99 by default,...) that were wiped out by the commits before.
Platforms tested:
Tested in TG-NCSA, both production and development mode.
(Still need to figure out the proper flag to use for Profile.)
Bug fix.
Description:
v8.0 -O3 infinite loops when compiling test/tselect.c. Use -O2.
Platforms tested:
Only tested in TG-NCSA, use both default and --disable-production options.
Description: For Intel 8.1 compiler, C99 standard has to be enabled to define macro ULLONG_MAX in its own header file limits.h.
Solution: Add flag -std=c99 to Intel compiler if the version is 8.1.
Platforms tested: Tested v1.6 because this is a very simple change.
Bug fix
Description:
"Teach" the configure scripts about Intel 7.1 compilers, which don't have
_quite_ the same compiler flags
Platforms tested:
Linux 2.4 (eirene)
Code cleanup/bug fix
Description:
Remove the undocumented "$NOFP" shell variable which would allow production
builds without removing the stack frame. This was cascading between C and
FORTRAN builds and causing problems.
Solution:
Hard-code removing the stack frame for now. Users would have needed to
read the configure scripts anyway, so there's not really much benefit to the
extra knob. Users who need this functionality (production builds with stack
frames) are debugging probably, so they will need to modify the script and
build their own version of the library now.
Platforms tested:
Linux 2.4 (verbena)
Too minor to require h5committest
