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/113956] [13/14 Regression] ice in gfc_trans_pointer_assignment, at fortran/trans-expr.cc:10524 Date: Tue, 09 Apr 2024 14:23:59 +0000 [thread overview] Message-ID: <bug-113956-4-RmdElp1Nwt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113956-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113956 --- Comment #7 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:88aea122a7ee639230bf17a9eda4bf8a5eb7e282 commit r14-9873-g88aea122a7ee639230bf17a9eda4bf8a5eb7e282 Author: Paul Thomas <pault@gcc.gnu.org> Date: Tue Apr 9 15:23:46 2024 +0100 Fortran: Fix ICE in gfc_trans_pointer_assignment [PR113956] 2024-04-09 Paul Thomas <pault@gcc.gnu.org> gcc/fortran PR fortran/113956 * trans-expr.cc (gfc_trans_pointer_assignment): Remove assert causing the ICE since it was unnecesary. gcc/testsuite/ PR fortran/113956 * gfortran.dg/pr113956.f90: New test.
next prev parent reply other threads:[~2024-04-09 14:24 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-16 8:20 [Bug fortran/113956] New: " dcb314 at hotmail dot com 2024-03-29 9:53 ` [Bug fortran/113956] [14 Regression] " dcb314 at hotmail dot com 2024-03-29 12:03 ` [Bug fortran/113956] [13/14 " anlauf at gcc dot gnu.org 2024-03-29 15:35 ` pault at gcc dot gnu.org 2024-03-29 16:37 ` anlauf at gcc dot gnu.org 2024-04-02 19:19 ` anlauf at gcc dot gnu.org 2024-04-03 13:06 ` pault at gcc dot gnu.org 2024-04-09 14:23 ` cvs-commit at gcc dot gnu.org [this message] 2024-04-17 13:34 ` law at gcc dot gnu.org 2024-05-08 8:06 ` [Bug fortran/113956] [13 " cvs-commit at gcc dot gnu.org 2024-05-08 8:08 ` 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-113956-4-RmdElp1Nwt@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).