public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/59107] [8/9/10/11 Regression] Spurious "Type specified for intrinsic function 'command_argument_count' at (1) is ignored" under -Wsurprising. Date: Mon, 11 May 2020 14:11:00 +0000 [thread overview] Message-ID: <bug-59107-4-LWlHrm5sik@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59107-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59107 --- Comment #22 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-8 branch has been updated by Mark Eggleston <markeggleston@gcc.gnu.org>: https://gcc.gnu.org/g:3d32b5c89438dbec423e48954ebffe51ee2b8dda commit r8-10247-g3d32b5c89438dbec423e48954ebffe51ee2b8dda Author: Mark Eggleston <markeggleston@gcc.gnu.org> Date: Mon May 11 12:38:14 2020 +0100 Fortran : Spurious warning message with -Wsurprising PR59107 This change is from a patch developed for gcc-5. The code has moved on since then requiring a change to interface.c 2020-05-11 Mark Eggleston <markeggleston@gcc.gnu.org> Backported from mainline 2020-05-11 Janus Weil <janus@gcc.gnu.org> Dominique d'Humieres <dominiq@lps.ens.fr> gcc/fortran/ PR fortran/59107 * gfortran.h: Rename field resolved as resolve_symbol_called and assign two 2 bits instead of 1. * interface.c (gfc_find_typebound_dtio_proc): Use new field name. * resolve.c (gfc_resolve_intrinsic): Replace check of the formal field with resolve_symbol_called is at least 2, if it is not set the field to 2. (resolve_symbol): Use new field name and check whether it is at least 1, if it is not set the field to 1. Backported from mainline 2020-05-11 Mark Eggleston <markeggleston@gcc.gnu.org> gcc/testsuite/ PR fortran/59107 * gfortran.dg/pr59107.f90: New test.
next prev parent reply other threads:[~2020-05-11 14:11 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-13 9:33 [Bug fortran/59107] New: " mathewc at nag dot co.uk 2013-11-17 15:14 ` [Bug fortran/59107] " janus at gcc dot gnu.org 2013-11-17 15:30 ` janus at gcc dot gnu.org 2013-11-17 15:39 ` janus at gcc dot gnu.org 2013-11-17 15:51 ` janus at gcc dot gnu.org 2013-11-17 15:58 ` janus at gcc dot gnu.org 2013-11-17 16:02 ` janus at gcc dot gnu.org 2013-11-17 16:18 ` [Bug fortran/59107] [4.7/4.8/4.9 Regression] " janus at gcc dot gnu.org 2013-11-17 19:01 ` janus at gcc dot gnu.org 2013-11-19 9:50 ` rguenth at gcc dot gnu.org 2014-06-12 13:49 ` [Bug fortran/59107] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:34 ` [Bug fortran/59107] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-01-22 14:27 ` dominiq at lps dot ens.fr 2015-03-21 15:27 ` dominiq at lps dot ens.fr 2015-06-23 8:27 ` [Bug fortran/59107] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 20:02 ` [Bug fortran/59107] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:32 ` jakub at gcc dot gnu.org 2020-05-11 8:27 ` [Bug fortran/59107] [8/9/10/11 " cvs-commit at gcc dot gnu.org 2020-05-11 9:45 ` cvs-commit at gcc dot gnu.org 2020-05-11 11:38 ` cvs-commit at gcc dot gnu.org 2020-05-11 14:11 ` cvs-commit at gcc dot gnu.org [this message] 2020-05-11 14:12 ` markeggleston at gcc dot gnu.org
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-59107-4-LWlHrm5sik@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).