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/96025] [10/11/12/13 Regression] ICE in expr_check_typed_help, at fortran/expr.c:5437 Date: Sun, 05 Mar 2023 19:36:44 +0000 [thread overview] Message-ID: <bug-96025-4-uil2lHitaO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96025-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96025 --- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:9db1287c8ced5425f6ef9d26b05a3eb9cbcc4b8d commit r10-11239-g9db1287c8ced5425f6ef9d26b05a3eb9cbcc4b8d Author: Harald Anlauf <anlauf@gmx.de> Date: Mon Feb 20 21:28:09 2023 +0100 Fortran: improve checking of character length specification [PR96025] gcc/fortran/ChangeLog: PR fortran/96025 * parse.c (check_function_result_typed): Improve type check of specification expression for character length and return status. (parse_spec): Use status from above. * resolve.c (resolve_fntype): Prevent use of invalid specification expression for character length. gcc/testsuite/ChangeLog: PR fortran/96025 * gfortran.dg/pr96025.f90: New test. (cherry picked from commit 6c1b825b3d6499dfeacf7c79dcf4b56a393ac204)
next prev parent reply other threads:[~2023-03-05 19:36 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-01 19:31 [Bug fortran/96025] New: [9/10/11 " gscfq@t-online.de 2020-07-01 19:32 ` [Bug fortran/96025] " gscfq@t-online.de 2020-07-01 20:19 ` dominiq at lps dot ens.fr 2020-07-01 21:21 ` kargl at gcc dot gnu.org 2020-07-01 21:21 ` kargl at gcc dot gnu.org 2020-07-02 6:43 ` rguenth at gcc dot gnu.org 2020-07-04 9:28 ` dominiq at lps dot ens.fr 2021-06-01 8:17 ` [Bug fortran/96025] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-05-27 9:43 ` [Bug fortran/96025] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:41 ` jakub at gcc dot gnu.org 2023-02-19 21:02 ` anlauf at gcc dot gnu.org 2023-02-20 20:43 ` anlauf at gcc dot gnu.org 2023-02-21 18:04 ` cvs-commit at gcc dot gnu.org 2023-03-04 19:51 ` cvs-commit at gcc dot gnu.org 2023-03-05 19:35 ` cvs-commit at gcc dot gnu.org 2023-03-05 19:36 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-05 19:38 ` anlauf 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-96025-4-uil2lHitaO@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).