public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/103471] Missed no IMPLICIT type errors
Date: Sun, 21 Apr 2024 16:34:05 +0000 [thread overview]
Message-ID: <bug-103471-4-E6aC6Fx4xx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103471-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103471
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[11/12/13/14 Regression] |Missed no IMPLICIT type
|ICE in |errors
|gfc_typenode_for_spec, at |
|fortran/trans-types.c:1114 |
--- Comment #12 from Paul Thomas <pault at gcc dot gnu.org> ---
The regression has been cured in the above commit and some of the missed error
messages have been fixed.
Compared with the submission to the list and discussed with Harald Anlauf, an
extra chunk has been added in resolve.cc(resolve_actual_arglist) to catch
untyped actual arguments.
See the testcase commented out line for an example interference between
different statements with untyped symbols.
I am keeping this one open having changed the summary.
Paul
prev parent reply other threads:[~2024-04-21 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 18:48 [Bug fortran/103471] New: [9/10/11/12 Regression] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:1114 gscfq@t-online.de
2021-11-30 7:03 ` [Bug fortran/103471] " rguenth at gcc dot gnu.org
2021-11-30 14:20 ` marxin at gcc dot gnu.org
2021-12-23 0:35 ` kargl at gcc dot gnu.org
2022-05-27 9:46 ` [Bug fortran/103471] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2023-07-07 10:41 ` [Bug fortran/103471] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-04-11 17:34 ` pault at gcc dot gnu.org
2024-04-18 20:38 ` anlauf at gcc dot gnu.org
2024-04-19 6:02 ` pault at gcc dot gnu.org
2024-04-19 6:02 ` pault at gcc dot gnu.org
2024-04-19 7:25 ` pault at gcc dot gnu.org
2024-04-21 16:24 ` cvs-commit at gcc dot gnu.org
2024-04-21 16:34 ` pault at gcc dot gnu.org [this message]
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-103471-4-E6aC6Fx4xx@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).