| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
the Autotools and CMake.
|
|
|
|
|
|
|
| |
https://bitbucket.hdfgroup.org/scm/hdffv/hdf5 into hdf5_1_12"
This reverts commit 9f9336a5bd541752f472bab4c93da8de89f862cd, reversing
changes made to 437a1919e7ba60fe75a33a466d264183a0255319.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* Changed version parsing from == gcc 4.x to < to handle ancient
compilers.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
I introduced in the last commit.
|
|
|
|
|
| |
changes to warnhist script (and some extra improvements for condensing C++
and Java warnings), and fixed a bunch of warnings.
|
| |
|
|
|
|
| |
clean up warnings.
|
| |
|
| |
|
|
|
|
| |
Commit Joe Lee's typo corrections for src/H5MF.c.
|
|
|
|
| |
building with debugging symbols.
|
| |
|
|
|
|
| |
as well as other minor rework and cleanup.
|
|
|
|
|
|
|
|
|
|
| |
hdf5_1_10
* commit '54957d37f5aa73912763dbb6e308555e863c43f4':
Commit copyright header change for src/H5PLpkg.c which was added after running script to make changes.
Add new files in release_docs to MANIFEST. Cimmit changes to Makefile.in(s) and H5PL.c that resulted from running autogen.sh.
Merge pull request #407 in HDFFV/hdf5 from ~LRKNOX/hdf5_lrk:hdf5_1_10_1 to hdf5_1_10_1
Change copyright headers to replace url referring to file to be removed and replace it with new url for COPYING file.
|
| |
|
|
|
|
|
| |
users can ignore -Wsuggest-attribute warnings and other
noise that doesn't indicate poor code quality.
|
|
|
|
|
|
|
|
| |
Remove -Wnormalized from GCC 4.x builds.
Tested on:
elk (w/gcc 4.4.7)
moohan (w/gcc 4.8.5)
|
|
|
|
|
|
|
|
| |
Update GNU compiler flags for 6.x release.
Tested on:
MacOSX/64 10.11.5 (amazon) w/serial, parallel & production
(h5committest forthcoming)
|
|
|
|
|
|
|
| |
production, etc. system.
Tested on: 64-bit Ubuntu 15.10 (Linux 4.2.0 x86_64) gcc 5.2.1
autotools serial - prod/debug w/ C++
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
--disable-symbols is specified and to ensure that production
mode (where symbol stripping is usually a part of the FLAGS)
doesn't conflict with --enable-symbols. This will allow better
(though still limited) debugging of production/optimized code.
The PGI, XLC, Intel, and Solaris files were not modified and
do not generate the symbol removal flag at this time. They'll
be updated in future check-ins. In the meantime, production
mode on those platforms still usually strips symbols.
This check-in also updates the Cygwin-specific files to use
the new autotools FLAGS and option scheme when uncommon
(non-gnu, etc.) Fortran compilers are used.
Tested on: 64-bit Ubuntu 15.10 (Linux 4.2.0 x86_64) gcc 5.2.1
autotools serial (prod/debug w/ and w/o symbols)
symbol presence/absence checked with objdump
|
|
|
|
|
| |
Tested on: 64-bit Ubuntu 15.10 (Linux 4.2.0 x86_64) gcc 5.2.1
serial autotools
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
debug
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
|
|
|
|
| |
Tested on: jam w/ gcc 5.2.0
|
|
|
|
|
|
|
| |
Protect gcc 5 debugging options
Tested on:
MacOSX/64 10.10.3 (amazon) w/gcc 5.1
|
|
|
|
|
|
|
|
|
| |
Clean up obsolete and unsupported versions of GCC, and update for GCC 5.1
release.
Tested on:
Mac OSX/64 10.10.3 (amazon) w/C++, FORTRAN, serial, production & parallel
(gcc 5.1 not available on other systems)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
script. The warnings that this generates cannot easily be resolved in
platform-independent C code since gnu expects the non-standard (gnu)
'D' suffix for double constants.
It's still technically useful for catching float and long double
constants, but should probably be enabled by developers on an
as-needed basis for that purpose so the spurious warnings are
avoided.
Tested on a local linux VM with gcc 4.8.2. This is a very minor change.
|
|
|
|
|
|
|
| |
Add new warning flags for gcc 4.9.x
Tested on:
MacOSX/64 10.9.3 (amazon) w/gcc 4.9.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
With optimization enabled, gcc 4.8 inserts garbage into the padding bytes of
floating point types when assigning from a literal constant. This caused
problems when H5detect.c scanned the bits in floating point types to determine
their properties.
Modified H5detect.c to scan for padding before further analyzing the type, and
to ignore all information in the padding areas. Also removed code that
temporarily disabled optimization.
Tested: jam, koala, ostrich, platypus (h5committest)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Clean up warnings, enable new compiler warning flag(s) and bring back
changes from Coverity branch:
r20813:
Remove the dead code as listed for coverity bug #1722. h5committested.
r20814:
Issue 69: Check return value and throw error if negative return. Also free datatype id on error
r20815:
Use HDstrncpy. --gh
r20816:
Replaced one last HDstrcat call with HDstrncat to resolve coverity issue 832.
r20817:
Use HDstrncpy and HDstrncat. --gh
r20818:
Purpose: Fix valgrind issues with h5jam
Description:
Modified h5jam to free strings strdup'd in parse_command_line before exit. Note
that they may still not be freed in case of error, due to the widespread use of
exit().
r20819:
Issue 80: change loop to use int as loop index.
r20820:
Maintenance: Fixed the bug found by coverity CID 788
There were two problems with this function:
1) it tried to unnecessary free NULL pointer
2) it tried to allocate c_name buffer that is done by H5Pget_class_name
Tested on:
Mac OSX 10.8.4 (amazon) w/gcc 4.8.1, C++ & FORTRAN
(too minor to require h5committest)
|
|
|
|
|
|
|
|
|
| |
double with GCC 4.8. A user in the forum found the
problem in H5detect.c (uninitialized buffer) and provided the solution. I checked it in yesterday. But it
turned out to be a false fix. So I'm back it out.
Tested on jam - reverse of changes.
|
|
|
|
|
|
|
|
| |
double with GCC 4.8. A user in the forum found the
problem in H5detect.c (uninitialized buffer) and provided the solution. Allen and I verified it.
Tested with h5committest and CMake on jam, koala, ostrich, playtus, and Allen's virtual machine.
|
|
|
|
|
|
|
|
|
|
|
| |
The new gcc v4.8.* compilers does not work well with dt_arith which failed
in production mode.
Solution:
A temporary patch by removing any optimization (-O*) from the PROD_CFLAGS
so that dt_arith will pass for now. A more through investigation is needed.
Tested: Jam and Koala where it failed and now passes.
|
|
|
|
|
|
|
| |
Update with new compiler warnings for gcc 4.8.x
Tested on:
Mac OSX/64 10.8.3 (amazon) w/gcc 4.8.0
|
|
|
|
|
|
|
| |
Update GCC compiler flags for new 4.7.0 release.
Tested on:
Mac OSX/64 10.7.3 (amazon) w/gcc 4.7.0
|
|
|
|
|
|
|
| |
gnu-flags
Don't add gcc flags for intel compiler even though its version display includes "gcc".
intel-flags
Extend intel version to include icc-12*.
|
|
|
|
|
|
|
| |
Remove C++ specific flag from C compilation flags, for gcc 4.5 & 4.6
Tested on:
FreebSD/64 8.2 (freedom) w/gcc 4.6
|
|
|
|
|
|
|
|
| |
Update with new warning flags for gcc 4.6.x
Tested on:
FreeBSD/32 8.2 (loyalty) w/gcc 4.6
FreeBSD/64 8.2 (freedom) w/gcc 4.6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix remaining aliasing problems and enable optimizations w/gcc now. This
addresses the remaining issues for Bug#1398.
Tested on:
FreeBSD/32 6.3 (duty) in debug mode
FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (jam) w/PGI compilers, w/default API=1.8.x,
w/C++ & FORTRAN, w/threadsafe, in debug mode
Linux/64-amd64 2.6 (amani) w/Intel compilers, w/default API=1.6.x,
w/C++ & FORTRAN, in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in debug mode
Linux/64-amd64 2.6 (abe) w/parallel, w/FORTRAN, in production mode
Mac OS X/32 10.6.3 (amazon) in debug mode
Mac OS X/32 10.6.3 (amazon) w/C++ & FORTRAN, w/threadsafe,
in production mode
|
|
|
|
|
|
|
|
| |
Add new warning flags for gcc 4.5.x
Tested on:
FreeBSD/32 6.3 (duty) w/gcc 4.5
FreeBSD/64 6.3 (liberty) w/gcc 4.5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
PathScale was mistaken as the Gcc compiler such that gcc flags were added
to it but PathScale did not honor many of them. (e.g. -Wvariadic-macros,
-Wold-style-definition, -Winit-self, -Wvariadic-macros, -Wmissing-include-dirs,
-Winit-self, -Wc++-compat)
Solution:
Added a pre-condition to detect pathScale compiler before Gcc is
accepted.
Tested:
Sandia Glory where PathScale compiler is available.
|
|
|
|
|
|
|
| |
Updated with new warning flags from gcc 4.4
Tested:
FreeBSD/64 6.3 (liberty) w/gcc 4.4.0
|