summaryrefslogtreecommitdiffstats
path: root/config/gnu-flags
Commit message (Collapse)AuthorAgeFilesLines
* Revise gnu-*flags and cmake/HDF*CompilerFlags.cmake files to add warningLarry Knox2020-05-181-60/+9
| | | | | | | flags for GCC compilers version 4.8 and above. Removed files from gnu-warnings that only apply to versions < 4.8. Consolidated warnings from versions < 4.8 that apply to versions >= 4.8 into the 4.8 warnings files.
* Restrict errors to gcc 4.8 and above.Allen Byrne2020-04-241-0/+2
|
* TRILAB-244 separate CXX warnings and errors from CAllen Byrne2020-04-231-19/+19
|
* Don't add general warnings flags for unsupported old versions of gcc andLarry Knox2020-04-201-2/+4
| | | | | | g++ (older than gcc/g++ 4.2). Correct gnu-cxxflags to determine warnings flags to be added based on C++ compiler version instead of C compiler version.
* Update all load_gcc_arguments to load_gnu_arguments.Larry Knox2020-04-091-11/+11
| | | | Fixes TRILAB-212.
* TRILAB-192 add c++ and fortran warnings build systems one fileAllen Byrne2020-04-051-26/+26
|
* Merge pull request #2402 in HDFFV/hdf5 from ↵David Young2020-03-231-74/+70
|\ | | | | | | | | | | | | | | | | | | ~DYOUNG/werror:break-out-warnings to develop * commit '2f09d8f3c8a4a44932c1b8ffb0f6ea2219059a5c': Move the GNU warnings configuration under config/gnu-warnings/ and trim the filename prefixes. Update config/gnu-flags to suit. By default, demote warnings promoted to errors back to warnings. Incorporate the H5_ECFLAGS into the library CFLAGS. Now a bunch of errors will occur. Next commit will demote the warnings promoted to errors back to warnings again. Break out warnings into more files that autoconf and CMake can share. This change temporarily disables the warnings that were promoted to errors, but I will add those warnings back as warnings, not errors, in the next commit.
| * Move the GNU warnings configuration under config/gnu-warnings/ and trimDavid Young2020-03-191-35/+35
| | | | | | | | | | | | | | the filename prefixes. Update config/gnu-flags to suit. I also made changes to config/cmake/HDFCompilerFlags.cmake, but I'm not sure they're correct.
| * By default, demote warnings promoted to errors back to warnings.David Young2020-02-251-1/+19
| |
| * Break out warnings into more files that autoconf and CMake can share. ThisDavid Young2020-02-251-70/+48
| | | | | | | | | | change temporarily disables the warnings that were promoted to errors, but I will add those warnings back as warnings, not errors, in the next commit.
* | Modfy expression to match mpicc build with Intel as intel compiler, notLarry Knox2020-02-271-1/+1
|/ | | | gcc.
* Merging in latest from upstream (HDFFV/hdf5:refs/heads/develop)Allen Byrne2020-01-241-1/+3
|\ | | | | | | | | | | | | | | | | | | | | * commit '590aaff33046df99a4d88ba59e4b461e060b36e4': Optimized the floating point comparisons a little bit. Fix for failing h5diff tests involving floating-point compares. Removed H5_DEC_ENUM Revert "Revert "Moved -Wunsuffixed-float-constants to the developer warnings."" Revert "Moved -Wunsuffixed-float-constants to the developer warnings." Moved -Wunsuffixed-float-constants to the developer warnings. Fixed a bug in testpar/t_cache.c concerning checking expected vs. actual cache entry reads and writes.
| * Revert "Revert "Moved -Wunsuffixed-float-constants to the developer warnings.""Dana Robinson2020-01-231-1/+3
| | | | | | | | This reverts commit 6486e06545bf637d46e18a787395542f4fca143a.
* | Create common build system files for warningsAllen Byrne2020-01-171-15/+31
|/
* Changed -Wformat-truncation's level from 2 to 1.Dana Robinson2020-01-011-1/+1
|
* 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
generated by cgit v0.12 at 2024-12-01 10:10:05 (GMT)