summaryrefslogtreecommitdiffstats
path: root/config/gnu-flags
Commit message (Collapse)AuthorAgeFilesLines
* Yanked -Wc++-compat from the flags used to build the C library in bothDana Robinson2019-12-041-1/+4
| | | | the Autotools and CMake.
* Revert "Make a squash commit of 'Quiet some warnings by adjusting warnings ↵David Young2019-11-271-87/+11
| | | | level and fixing some code.' (commit 5c911d8baf3)"
* Always warn on maybe-uninitialized. -Wincompatible-pointer-types was notDavid Young2019-11-221-2/+2
| | | | available until GCC 5, so enable it only if that's the GCC version we're using.
* Only promote maybe-uninitialized warnings to errors on GCC 8. Even onDavid Young2019-11-221-1/+7
| | | | | GCC 8, there may be false positives at low optimization levels? I need to check.
* Only use -Werror=cast-function-type with GCC 8 and later.David Young2019-11-221-1/+1
|
* Put all of the -W options back into the order I found them in so that it'sDavid Young2019-11-221-29/+23
| | | | easier to compare old and new config/gnu-flags.
* Promote decleration-after-statement warnings to errors.David Young2019-11-131-1/+1
|
* Make errors of some more warnings. Move disabled warnings toDavid Young2019-11-131-31/+43
| | | | | DEVELOPER_WARNING_CFLAGS. Put just one warning option on a line, and sort some of the options.
* Change some GCC warnings to errors. Fix code to quiet some warnings.David Young2019-11-051-11/+75
|
* Fixed a couple of typos.Dana Robinson2019-08-011-1/+1
|
* Restored warnings for older gcc so jam can continue to creak along.Dana Robinson2019-07-161-2/+12
|
* Removed support for gcc 4.3 and earlier.Dana Robinson2019-07-141-11/+1
|
* Fix errant quotesDana Robinson2019-07-101-1/+1
|
* * Fixed a bug in the gcc warning parsingDana Robinson2019-07-101-8/+8
| | | | | * Changed version parsing from == gcc 4.x to < to handle ancient compilers.
* Reworked the config/gnu-flags file to be more organized and robust.Dana Robinson2019-07-101-82/+82
|
* Converted duplicated flags code to a set of if statements.Dana Robinson2019-07-101-435/+117
|
* Added GCC9 flags to CMake buildQuincey Koziol2019-07-031-1/+0
|
* Add support for GCC9, update warnhist script, and clean up warnings.Quincey Koziol2019-07-031-10/+61
|
* Move the -Wformat-nonliteral warning to the developer flags. Fix bugsQuincey Koziol2019-06-291-2/+5
| | | | I introduced in the last commit.
* Updated configure & CMake compiler flags for GCC 8.x, along with correspondingQuincey Koziol2019-06-281-11/+61
| | | | | changes to warnhist script (and some extra improvements for condensing C++ and Java warnings), and fixed a bunch of warnings.
* Move -Wnormalized down into GCC 6.x flagsQuincey Koziol2019-06-221-3/+3
|
* Add support for GCC 7.x warnings, update warnhist script to account for them,Quincey Koziol2019-06-211-3/+47
| | | | clean up warnings.
* HDFFV-10776 missing compiler flagsAllen Byrne2019-04-301-9/+9
|
* Correct typo in comment in config/gnu-flags.Larry Knox2018-07-241-1/+1
|
* Apply Cygwin pathches from Marco Atzeri.Larry Knox2018-07-181-1/+13
| | | | Commit Joe Lee's typo corrections for src/H5MF.c.
* Added -fno-omit-frame-pointer to gcc flags when symbols whenDana Robinson2017-06-121-1/+1
| | | | building with debugging symbols.
* Fixed misplaced space in config/gnu-flags.Dana Robinson2017-05-261-1/+1
|
* Updated the gnu-flags config file to remove gcc 3.x and 4.0 configurationsDana Robinson2017-05-161-607/+88
| | | | as well as other minor rework and cleanup.
* Merge pull request #426 in HDFFV/hdf5 from ~LRKNOX/hdf5_lrk:hdf5_1_10 to ↵Larry Knox2017-04-251-6/+4
| | | | | | | | | | 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.
* Updated the developer flags so that they respect gcc versions.Dana Robinson2017-01-121-19/+87
|
* Added an --enable-developer-warnings option to configure soDana Robinson2017-01-101-24/+16
| | | | | users can ignore -Wsuggest-attribute warnings and other noise that doesn't indicate poor code quality.
* [svn-r30026] Description:Quincey Koziol2016-06-061-9/+9
| | | | | | | | Remove -Wnormalized from GCC 4.x builds. Tested on: elk (w/gcc 4.4.7) moohan (w/gcc 4.8.5)
* [svn-r30015] Description:Quincey Koziol2016-06-051-25/+97
| | | | | | | | Update GNU compiler flags for 6.x release. Tested on: MacOSX/64 10.11.5 (amazon) w/serial, parallel & production (h5committest forthcoming)
* [svn-r29131] Updated the GNU g++ compiler config file to use the new debug/Dana Robinson2016-02-171-1/+1
| | | | | | | 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++
* [svn-r29129] Added NO_SYMBOLS_CFLAGS, etc. to allow stripping symbols whenDana Robinson2016-02-171-3/+1
| | | | | | | | | | | | | | | | | | | | --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
* [svn-r29023] Fixed typos in symbols flags that prevented using -g, etc.Dana Robinson2016-02-011-2/+2
| | | | | Tested on: 64-bit Ubuntu 15.10 (Linux 4.2.0 x86_64) gcc 5.2.1 serial autotools
* [svn-r28996] Autotools configure updates to allow separation of build type, ↵Dana Robinson2016-01-271-11/+36
| | | | | | | | | | | | | | 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
* [svn-r27722] Updated the gnu config to cover gcc 5.2*.Dana Robinson2015-09-091-1/+1
| | | | Tested on: jam w/ gcc 5.2.0
* [svn-r27066] Description:Quincey Koziol2015-05-151-1/+8
| | | | | | | Protect gcc 5 debugging options Tested on: MacOSX/64 10.10.3 (amazon) w/gcc 5.1
* [svn-r27060] Description:Quincey Koziol2015-05-141-161/+90
| | | | | | | | | 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)
* [svn-r25756] Removed the -Wunsuffixed-float-constants warning from the gnu-flagsDana Robinson2014-10-311-1/+1
| | | | | | | | | | | | | 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.
* [svn-r25206] Description:Quincey Koziol2014-05-201-3/+79
| | | | | | | Add new warning flags for gcc 4.9.x Tested on: MacOSX/64 10.9.3 (amazon) w/gcc 4.9.0
* [svn-r24171] Purpose: Fix problem with gcc 4.8Neil Fortner2013-09-191-5/+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)
* [svn-r24101] Description:Quincey Koziol2013-09-051-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* [svn-r24098] Issue 8500 - H5detect.c has trouble to find info for long ↵Raymond Lu2013-09-041-0/+5
| | | | | | | | | 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.
* [svn-r24095] Issue 8500 - H5detect.c has trouble to find info for long ↵Raymond Lu2013-09-031-5/+0
| | | | | | | | 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.
* [svn-r24017] Bug fix: HDFFV-8500Albert Cheng2013-08-161-0/+5
| | | | | | | | | | | 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.
* [svn-r23584] Description:Quincey Koziol2013-04-131-6/+77
| | | | | | | Update with new compiler warnings for gcc 4.8.x Tested on: Mac OSX/64 10.8.3 (amazon) w/gcc 4.8.0
* [svn-r22222] Description:Quincey Koziol2012-04-011-1/+75
| | | | | | | Update GCC compiler flags for new 4.7.0 release. Tested on: Mac OSX/64 10.7.3 (amazon) w/gcc 4.7.0
* [svn-r22020] Fix for HDFFV-7878.Larry Knox2012-03-031-1/+7
| | | | | | | 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*.
generated by cgit v0.12 at 2024-11-01 15:27:19 (GMT)