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/106985] ICE in gfc_simplify_expr, at fortran/expr.cc:2290 Date: Fri, 30 Sep 2022 20:33:23 +0000 [thread overview] Message-ID: <bug-106985-4-owzFdivepp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106985-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106985 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:0a4fff071ff48d699b1af94b88f8878da006c770 commit r11-10282-g0a4fff071ff48d699b1af94b88f8878da006c770 Author: Harald Anlauf <anlauf@gmx.de> Date: Tue Sep 20 22:23:43 2022 +0200 Fortran: NULL pointer dereference in invalid simplification [PR106985] gcc/fortran/ChangeLog: PR fortran/106985 * expr.c (gfc_simplify_expr): Avoid NULL pointer dereference. gcc/testsuite/ChangeLog: PR fortran/106985 * gfortran.dg/pr106985.f90: New test. (cherry picked from commit 8dbb15bc2d019488240c1e69d93121b0347ac092)
next prev parent reply other threads:[~2022-09-30 20:33 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-20 17:34 [Bug fortran/106985] New: " gscfq@t-online.de 2022-09-20 19:09 ` [Bug fortran/106985] " anlauf at gcc dot gnu.org 2022-09-20 20:26 ` cvs-commit at gcc dot gnu.org 2022-09-20 20:35 ` anlauf at gcc dot gnu.org 2022-09-29 18:39 ` cvs-commit at gcc dot gnu.org 2022-09-30 20:33 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-30 20:33 ` cvs-commit 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-106985-4-owzFdivepp@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).