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/103471] [11/12/13/14 Regression] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:1114 Date: Sun, 21 Apr 2024 16:24:36 +0000 [thread overview] Message-ID: <bug-103471-4-nqcXmTn6wb@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 --- Comment #11 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Paul Thomas <pault@gcc.gnu.org>: https://gcc.gnu.org/g:f17d31e709af9b2d488adecd6cd040dfc1f23b04 commit r14-10059-gf17d31e709af9b2d488adecd6cd040dfc1f23b04 Author: Paul Thomas <pault@gcc.gnu.org> Date: Sun Apr 21 17:24:24 2024 +0100 Fortran: Detect 'no implicit type' error in right place [PR103471] 2024-04-21 Paul Thomas <pault@gcc.gnu.org> gcc/fortran PR fortran/103471 * resolve.cc (resolve_actual_arglist): Catch variables silently set as untyped, resetting the flag so that gfc_resolve_expr can generate the no implicit type error. (gfc_resolve_index_1): Block index expressions of unknown type from being converted to default integer, avoiding the fatal error in trans-decl.cc. * symbol.cc (gfc_set_default_type): Remove '(symbol)' from the 'no IMPLICIT type' error message. * trans-decl.cc (gfc_get_symbol_decl): Change fatal error locus to that of the symbol declaration. (gfc_trans_deferred_vars): Remove two trailing tabs. gcc/testsuite/ PR fortran/103471 * gfortran.dg/pr103471.f90: New test.
next prev parent reply other threads:[~2024-04-21 16:24 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 " 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 [this message] 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-nqcXmTn6wb@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).