public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/96320] gfortran 8-10 shape mismatch in assumed-length dummy argument character array
Date: Tue, 28 Jul 2020 10:32:50 +0000 [thread overview]
Message-ID: <bug-96320-4-blPd1ouAQP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96320-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96320
--- Comment #16 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Bother - I left the diagnostic line in the patch:
>
> + gfc_warning_now (0, "s1 %i s2 %i \n", s1->as->type, s2->as->type);
>
>Sorry about that
What I guessed, but I still see (not new)
/opt/gcc/work/gcc/testsuite/gfortran.dg/whole_file_23.f90:18:32:
18 | pure integer function lensum (words, sep)
| 1
Warning: Interface mismatch in global procedure 'lensum' at (1): Shape mismatch
in argument 'words'
next prev parent reply other threads:[~2020-07-28 10:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 4:47 [Bug fortran/96320] New: " damian at sourceryinstitute dot org
2020-07-26 16:34 ` [Bug fortran/96320] " dominiq at lps dot ens.fr
2020-07-26 16:44 ` damian at sourceryinstitute dot org
2020-07-26 16:54 ` dominiq at lps dot ens.fr
2020-07-26 18:43 ` kargl at gcc dot gnu.org
2020-07-26 19:13 ` kargl at gcc dot gnu.org
2020-07-26 21:35 ` jvdelisle at charter dot net
2020-07-27 0:39 ` damian at sourceryinstitute dot org
2020-07-27 0:45 ` sgk at troutmask dot apl.washington.edu
2020-07-27 3:34 ` damian at sourceryinstitute dot org
2020-07-27 7:26 ` pault at gcc dot gnu.org
2020-07-27 11:37 ` dominiq at lps dot ens.fr
2020-07-27 17:26 ` pault at gcc dot gnu.org
2020-07-27 18:12 ` damian at sourceryinstitute dot org
2020-07-27 19:03 ` dominiq at lps dot ens.fr
2020-07-28 9:24 ` dominiq at lps dot ens.fr
2020-07-28 9:43 ` paul.richard.thomas at gmail dot com
2020-07-28 10:32 ` dominiq at lps dot ens.fr [this message]
2020-07-28 14:13 ` sgk at troutmask dot apl.washington.edu
2020-07-28 15:18 ` dominiq at lps dot ens.fr
2020-08-02 10:00 ` cvs-commit at gcc dot gnu.org
2020-08-02 10:05 ` pault at gcc dot gnu.org
2020-08-03 23:45 ` damian at sourceryinstitute dot org
2020-08-04 1:53 ` sgk at troutmask dot apl.washington.edu
2020-08-15 1:59 ` damian at sourceryinstitute dot org
2020-08-20 17:17 ` damian at sourceryinstitute dot org
2020-12-28 14:55 ` cvs-commit at gcc dot gnu.org
2021-01-04 14:42 ` cvs-commit at gcc dot gnu.org
2021-01-04 15:15 ` pault at gcc dot gnu.org
2021-01-21 10:01 ` cvs-commit at gcc dot gnu.org
2023-10-31 14:17 ` pault 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-96320-4-blPd1ouAQP@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: link
Be 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).