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/100551] [11/12 Regression] Passing return value of intrinsic to class(*) dummy argument can cause segfaults Date: Sun, 23 May 2021 18:52:16 +0000 [thread overview] Message-ID: <bug-100551-4-q1AtKR5gqe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100551-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100551 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:fe03f4fc9548b3fdbff3c8284a994feaa7d6307d commit r12-1005-gfe03f4fc9548b3fdbff3c8284a994feaa7d6307d Author: Harald Anlauf <anlauf@gmx.de> Date: Sun May 23 20:51:14 2021 +0200 Fortran: fix passing return value to class(*) dummy argument gcc/fortran/ChangeLog: PR fortran/100551 * trans-expr.c (gfc_conv_procedure_call): Adjust check for implicit conversion of actual argument to an unlimited polymorphic procedure argument. gcc/testsuite/ChangeLog: PR fortran/100551 * gfortran.dg/pr100551.f90: New test.
next prev parent reply other threads:[~2021-05-23 18:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-11 21:32 [Bug fortran/100551] New: " bugs at colin dot moe 2021-05-12 7:12 ` [Bug fortran/100551] " rguenth at gcc dot gnu.org 2021-05-12 9:41 ` marxin at gcc dot gnu.org 2021-05-12 20:22 ` anlauf at gcc dot gnu.org 2021-05-12 21:11 ` anlauf at gcc dot gnu.org 2021-05-13 7:41 ` anlauf at gcc dot gnu.org 2021-05-20 21:30 ` anlauf at gcc dot gnu.org 2021-05-23 18:52 ` cvs-commit at gcc dot gnu.org [this message] 2021-05-25 20:13 ` cvs-commit at gcc dot gnu.org 2021-05-25 20:16 ` anlauf at gcc dot gnu.org 2022-01-07 17:47 ` 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-100551-4-q1AtKR5gqe@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).