This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [Patch, Fortran, committed] PR36518 - Enable -Werror for libgfortran and fix a warning
- From: IainS <developer at sandoe-acoustics dot co dot uk>
- To: Tobias Burnus <tobias dot burnus at physik dot fu-berlin dot de>
- Cc: Fortran Fortran Fortran List <fortran at gcc dot gnu dot org>
- Date: Fri, 13 Jun 2008 20:47:09 +0100
- Subject: Re: [Patch, Fortran, committed] PR36518 - Enable -Werror for libgfortran and fix a warning
- References: <20080613193115.GA13219@physik.fu-berlin.de>
On 13 Jun 2008, at 20:31, Tobias Burnus wrote:
The choice not to build libgfortran with -Werror is, I think,
deliberate. Due to the large number of targets on which we have to
build, we shouldn't do it, it will just be too much pain. (I haven't
resources to do a bootstrap right now, but I'm for example almost
sure
that with the mingw headers, you'll get some warnings, e.g. about
formats.)
Can you try to dig them up? Maybe we can fix some of those warnings.
(Does not need to be now, but I would like to see all warnings be
fixed. Too bad that the testresults@ do not contain such a list, I
think
it would be helpful to fix some of the bugs.)
my build script keeps a log ... here's the output from a bootstrap
a couple of hours ago
powerpc-apple-darwin8 as of 136717
grep libgfortran warnings.txt
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/all_l1.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'long int'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/all_l2.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'long int'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/all_l4.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'long int'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/all_l8.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'long int'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/any_l1.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'long int'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/any_l4.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'long int'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/any_l2.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'long int'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/any_l8.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'long int'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/
count_1_l.c:142: warning: format '%d' expects type 'int', but
argument 2 has type 'long int'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/
count_2_l.c:142: warning: format '%d' expects type 'int', but
argument 2 has type 'long int'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/
count_4_l.c:142: warning: format '%d' expects type 'int', but
argument 2 has type 'long int'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/
count_8_l.c:142: warning: format '%d' expects type 'int', but
argument 2 has type 'long int'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/all_l1.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/all_l2.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/all_l4.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/all_l8.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/all_l16.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/any_l1.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/any_l2.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/any_l4.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/any_l8.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/any_l16.c:
142: warning: format '%d' expects type 'int', but argument 2 has type
'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/
count_1_l.c:142: warning: format '%d' expects type 'int', but
argument 2 has type 'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/
count_2_l.c:142: warning: format '%d' expects type 'int', but
argument 2 has type 'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/
count_4_l.c:142: warning: format '%d' expects type 'int', but
argument 2 has type 'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/
count_8_l.c:142: warning: format '%d' expects type 'int', but
argument 2 has type 'index_type'
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/generated/
count_16_l.c:142: warning: format '%d' expects type 'int', but
argument 2 has type 'index_type'
which you've fixed....
/Volumes/UFSScratch/GCC/gcc-4-4-trunk/libgfortran/io/fbuf.c:160:
warning: comparison between signed and unsigned
which Dominique already mentioned.
So not too too bad on this platform ...
Iain