public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rimvydas.jas at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/102145] TKR mismatches with -pedantic: -fallow-argument-mismatch does not degrade errors to warnings Date: Sun, 12 Sep 2021 23:40:31 +0000 [thread overview] Message-ID: <bug-102145-4-O5x66JMUuJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102145-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102145 --- Comment #9 from Rimvydas (RJ) <rimvydas.jas at gmail dot com> --- (In reply to Steve Kargl from comment #8) > Yes, it should behave like -pedantic-errors. Actually no, -pedantic is equivalent to -Wpedantic, while -pedantic-errors is -Werror=pedantic. Rest is interpretation vs expectation. > -fallow-argument-mismatch was added to allow users, > who refuse to fix their code, the ability to downgrade the error > to a warning. If -pedantic changes -fallow-argument-mismatch > back to an error, then don't use -pedantic. The -std=legacy already implies -fallow-argument-mismatch and wrongfully warns by default. Consider gfortran -std=legacy -Wpedantic -Wno-error=pedantic -c. > And, no, the code was not "carefully crafted". Code, which exploits > argument mismatch, has always been invalid Fortran. It is time that > those codes are fixed. Until every compiler vendor agree on universal module format for things like "USE MPI" or "USE MPI_F08", the HPC applications will continue to use F77 "mpif.h" include, unless "buffer" type would get standardized. Many projects already split things like: call mpi_foo(1, MPI_INTEGER, N); ..... ; call mpi_foo(1., MPI_REAL, N) into separate compilable sources and in the end such compiler behavior change solved nothing other than creating lots unnecessary work for users and package maintainers for every different OS. It will become more evident when more HPC systems get replaced from older LTS having older versions of gfortran.
next prev parent reply other threads:[~2021-09-12 23:40 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-31 14:59 [Bug fortran/102145] New: " ripero84 at gmail dot com 2021-08-31 17:24 ` [Bug fortran/102145] " kargl at gcc dot gnu.org 2021-09-08 14:14 ` ripero84 at gmail dot com 2021-09-08 16:51 ` sgk at troutmask dot apl.washington.edu 2021-09-12 19:08 ` rimvydas.jas at gmail dot com 2021-09-12 19:09 ` rimvydas.jas at gmail dot com 2021-09-12 19:22 ` kargl at gcc dot gnu.org 2021-09-12 19:34 ` rimvydas.jas at gmail dot com 2021-09-12 22:56 ` sgk at troutmask dot apl.washington.edu 2021-09-12 23:40 ` rimvydas.jas at gmail dot com [this message] 2021-09-13 2:52 ` sgk at troutmask dot apl.washington.edu 2021-09-13 5:18 ` rimvydas.jas at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-102145-4-O5x66JMUuJ@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).