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/94578] Incorrect assignment of RESHAPE() result to a Fortran pointer Date: Sat, 25 Apr 2020 10:29:53 +0000 [thread overview] Message-ID: <bug-94578-4-EUpnhQlNsK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94578-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94578 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Thomas Kथà¤nig <tkoenig@gcc.gnu.org>: https://gcc.gnu.org/g:cf3f7b309ffdd888fdd85048ac9b4bcdc2713a45 commit r10-7960-gcf3f7b309ffdd888fdd85048ac9b4bcdc2713a45 Author: Thomas König <tkoenig@gcc.gnu.org> Date: Sat Apr 25 12:28:15 2020 +0200 Fix PR 94578. Our intrinsics do not handle spans on their return values (yet), so this creates a temporary for subref array pointers. 2020-04-25 Thomas Koenig <tkoenig@gcc.gnu.org> PR fortran/94578 * trans-expr.c (arrayfunc_assign_needs_temporary): If the LHS is a subref pointer, we also need a temporary. 2020-04-25 Thomas Koenig <tkoenig@gcc.gnu.org> PR fortran/94578 * gfortran.dg/pointer_assign_14.f90: New test. * gfortran.dg/pointer_assign_15.f90: New test.
next prev parent reply other threads:[~2020-04-25 10:29 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-13 13:46 [Bug fortran/94578] New: " howisjw at hotmail dot com 2020-04-13 13:53 ` [Bug fortran/94578] " howisjw at hotmail dot com 2020-04-13 13:56 ` howisjw at hotmail dot com 2020-04-14 15:05 ` tkoenig at gcc dot gnu.org 2020-04-14 15:08 ` tkoenig at gcc dot gnu.org 2020-04-16 14:21 ` tkoenig at gcc dot gnu.org 2020-04-16 14:24 ` tkoenig at gcc dot gnu.org 2020-04-17 7:02 ` howisjw at hotmail dot com 2020-04-17 14:16 ` tkoenig at gcc dot gnu.org 2020-04-17 15:17 ` tkoenig at gcc dot gnu.org 2020-04-25 10:29 ` cvs-commit at gcc dot gnu.org [this message] 2020-04-27 9:42 ` howisjw at hotmail dot com 2020-04-27 16:57 ` tkoenig 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-94578-4-EUpnhQlNsK@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).