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/95500] Segfault compiling extra interface on intrinsic Date: Fri, 05 Jun 2020 18:46:47 +0000 [thread overview] Message-ID: <bug-95500-4-bJIhs6OEd3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95500-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95500 --- Comment #4 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:4b3ea558da6479dabe5841bcb0f6bad3f7fea858 commit r10-8250-g4b3ea558da6479dabe5841bcb0f6bad3f7fea858 Author: Harald Anlauf <anlauf@gmx.de> Date: Thu Jun 4 21:00:33 2020 +0200 PR fortran/95500 - Segfault compiling extra interface on intrinsic Converting an expression so that it can be passed by reference could result in a NULL pointer dereference. 2020-06-04 Steven G. Kargl <kargl@gcc.gnu.org> Harald Anlauf <anlauf@gmx.de> gcc/fortran/ PR fortran/95500 * trans-expr.c (gfc_conv_expr_reference): Do not dereference NULL pointer. gcc/testsuite/ PR fortran/95500 * gfortran.dg/pr95500.f90: New test. (cherry picked from commit 8c727bdf4acf28c8315b119a1c8f6d6af745c2af)
next prev parent reply other threads:[~2020-06-05 18:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-03 15:13 [Bug fortran/95500] New: " vincent.lafage at in2p3 dot fr 2020-06-03 15:43 ` [Bug fortran/95500] " kargl at gcc dot gnu.org 2020-06-04 18:53 ` anlauf at gcc dot gnu.org 2020-06-04 19:01 ` cvs-commit at gcc dot gnu.org 2020-06-05 18:46 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-05 18:51 ` cvs-commit at gcc dot gnu.org 2020-06-05 18:52 ` 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-95500-4-bJIhs6OEd3@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).