public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/103471] [9/10/11/12 Regression] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:1114 Date: Thu, 23 Dec 2021 00:35:40 +0000 [thread overview] Message-ID: <bug-103471-4-bwbSsEnJ7R@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 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kargl at gcc dot gnu.org --- Comment #2 from kargl at gcc dot gnu.org --- An error is being queued in symbol.c(gfc_set_default_type), but error reporting has been disabled for some reason. Changing gfc_error() to gfc_error_now() restores emitting the error message, but is this correct! diff --git a/gcc/fortran/symbol.c b/gcc/fortran/symbol.c index 179f6029ca3..43691710120 100644 --- a/gcc/fortran/symbol.c +++ b/gcc/fortran/symbol.c @@ -303,11 +303,11 @@ gfc_set_default_type (gfc_symbol *sym, int error_flag, gfc_namespace *ns) { const char *guessed = lookup_symbol_fuzzy (sym->name, sym); if (guessed) - gfc_error ("Symbol %qs at %L has no IMPLICIT type" + gfc_error_now ("Symbol %qs at %L has no IMPLICIT type" "; did you mean %qs?", sym->name, &sym->declared_at, guessed); else - gfc_error ("Symbol %qs at %L has no IMPLICIT type", + gfc_error_now ("Symbol %qs at %L has no IMPLICIT type", sym->name, &sym->declared_at); sym->attr.untyped = 1; /* Ensure we only give an error once. */ }
next prev parent reply other threads:[~2021-12-23 0:35 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-29 18:48 [Bug fortran/103471] New: " 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 [this message] 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 ` [Bug fortran/103471] Missed no IMPLICIT type errors 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-103471-4-bwbSsEnJ7R@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).