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/108421] ICE in get_expr_storage_size, at fortran/interface.cc:2862 Date: Sun, 05 Feb 2023 18:55:11 +0000 [thread overview] Message-ID: <bug-108421-4-Ey4Dd8HuVg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108421-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108421 --- Comment #7 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:068fce9743ec9f3181c189cb8d03a982ca30eb7e commit r10-11194-g068fce9743ec9f3181c189cb8d03a982ca30eb7e Author: Harald Anlauf <anlauf@gmx.de> Date: Mon Jan 16 21:30:56 2023 +0100 Fortran: fix ICE in get_expr_storage_size [PR108421] gcc/fortran/ChangeLog: PR fortran/108421 * interface.c (get_expr_storage_size): Check that we actually have an integer value before trying to extract it with mpz_get_si. gcc/testsuite/ChangeLog: PR fortran/108421 * gfortran.dg/pr108421.f90: New test. (cherry picked from commit a75760374ee54768e5fd6a27080698bfbbd041ab)
prev parent reply other threads:[~2023-02-05 18:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-16 17:48 [Bug fortran/108421] New: " gscfq@t-online.de 2023-01-16 20:04 ` [Bug fortran/108421] " anlauf at gcc dot gnu.org 2023-01-16 21:12 ` anlauf at gcc dot gnu.org 2023-01-17 19:39 ` cvs-commit at gcc dot gnu.org 2023-01-17 19:41 ` anlauf at gcc dot gnu.org 2023-01-28 21:45 ` cvs-commit at gcc dot gnu.org 2023-02-04 15:43 ` cvs-commit at gcc dot gnu.org 2023-02-05 18:55 ` cvs-commit 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-108421-4-Ey4Dd8HuVg@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).