public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/54724] New: libgfortran does not respect --disable-werror
@ 2012-09-27 5:24 vapier at gentoo dot org
2012-09-28 10:12 ` [Bug fortran/54724] " burnus at gcc dot gnu.org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: vapier at gentoo dot org @ 2012-09-27 5:24 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54724
Bug #: 54724
Summary: libgfortran does not respect --disable-werror
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: vapier@gentoo.org
the --disable-werror flag is very useful for distributions and dealing with a
myriad of build systems / versions / etc... unfortunately, libgfortran doesnt
respect this flag.
# Add -Wall -fno-repack-arrays -fno-underscoring if we are using GCC.
if test "x$GCC" = "xyes"; then
AM_FCFLAGS="-I . -Wall -Werror -fimplicit-none -fno-repack-arrays
-fno-underscoring"
...
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug fortran/54724] libgfortran does not respect --disable-werror
2012-09-27 5:24 [Bug fortran/54724] New: libgfortran does not respect --disable-werror vapier at gentoo dot org
@ 2012-09-28 10:12 ` burnus at gcc dot gnu.org
2012-09-28 23:20 ` vapier at gentoo dot org
2014-12-09 20:24 ` dominiq at lps dot ens.fr
2 siblings, 0 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2012-09-28 10:12 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54724
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-09-28 10:12:00 UTC ---
Well, libgfortran only uses -Werror for the Fortran code. I think it is
extremely unlikely to trigger there. (That part uses no system-specific code.)
Using -Werror for libgfortran's C code would be nice, but it fails too often.
(I tried it once.) Thus, libgfortran's C code is compiled without -Werror by
default - even without an explicit --disable-werror.
Thus, I think your issue is rather hypothetical and I don't think it makes
sense to fix it.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug fortran/54724] libgfortran does not respect --disable-werror
2012-09-27 5:24 [Bug fortran/54724] New: libgfortran does not respect --disable-werror vapier at gentoo dot org
2012-09-28 10:12 ` [Bug fortran/54724] " burnus at gcc dot gnu.org
@ 2012-09-28 23:20 ` vapier at gentoo dot org
2014-12-09 20:24 ` dominiq at lps dot ens.fr
2 siblings, 0 replies; 4+ messages in thread
From: vapier at gentoo dot org @ 2012-09-28 23:20 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54724
--- Comment #2 from Mike Frysinger <vapier at gentoo dot org> 2012-09-28 23:20:09 UTC ---
i'm 50/50 on this. if the code doesn't utilize anything beyond the local code
base, and isn't compiled/processed by anything other than the local compiler,
then the -Werror shouldn't be a problem. but i noticed -Werror was being used
because some flags *were* causing warnings and so the build errored out (bug
54725). granted, this warning was valid and it's good that it broke (otherwise
i might not have noticed as soon as i did), but in general, it's indeterminate
warnings like that why distros want to turn off -Werror in their builds.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/54724] libgfortran does not respect --disable-werror
2012-09-27 5:24 [Bug fortran/54724] New: libgfortran does not respect --disable-werror vapier at gentoo dot org
2012-09-28 10:12 ` [Bug fortran/54724] " burnus at gcc dot gnu.org
2012-09-28 23:20 ` vapier at gentoo dot org
@ 2014-12-09 20:24 ` dominiq at lps dot ens.fr
2 siblings, 0 replies; 4+ messages in thread
From: dominiq at lps dot ens.fr @ 2014-12-09 20:24 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54724
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
(1) I think that using --disable-werror is a very bad idea.
(2) I cannot remember a single instance of libgfortran being broken because of
-Werror.
So I agree with Tobias:
> Thus, I think your issue is rather hypothetical and I don't think it makes
> sense to fix it.
Thus closing as WONTFIX.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-12-09 20:24 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-09-27 5:24 [Bug fortran/54724] New: libgfortran does not respect --disable-werror vapier at gentoo dot org
2012-09-28 10:12 ` [Bug fortran/54724] " burnus at gcc dot gnu.org
2012-09-28 23:20 ` vapier at gentoo dot org
2014-12-09 20:24 ` dominiq at lps dot ens.fr
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).