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/41453] use INTENT(out) for optimization Date: Sun, 25 Sep 2022 12:48:32 +0000 [thread overview] Message-ID: <bug-41453-4-GRjMehMSq3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-41453-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41453 --- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Mikael Morin <mikael@gcc.gnu.org>: https://gcc.gnu.org/g:95375ffb3dd59f51e79408dd3b2b620dc1af71b1 commit r13-2840-g95375ffb3dd59f51e79408dd3b2b620dc1af71b1 Author: Mikael Morin <mikael@gcc.gnu.org> Date: Thu Sep 1 11:27:36 2022 +0200 fortran: Support clobbering of allocatables and pointers [PR41453] This adds support for clobbering of allocatable and pointer scalar variables passed as actual argument to a subroutine when the associated dummy has the INTENT(OUT) attribute. Support was explicitly disabled (since the beginning for pointers, since r11-7315-g2df374b337a5f6cf5528e91718e4e12e4006b7ae for allocatables), but the clobber generation code seems to support it well, as demonstrated by the newly added testcase. PR fortran/41453 PR fortran/99169 gcc/fortran/ChangeLog: * trans-expr.cc (gfc_conv_procedure_call): Remove conditions on ALLOCATABLE and POINTER attributes guarding clobber generation. gcc/testsuite/ChangeLog: * gfortran.dg/intent_optimize_9.f90: New test.
next prev parent reply other threads:[~2022-09-25 12:48 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-41453-4@http.gcc.gnu.org/bugzilla/> 2012-06-29 14:26 ` [Bug middle-end/41453] " Joost.VandeVondele at mat dot ethz.ch 2013-03-29 9:04 ` Joost.VandeVondele at mat dot ethz.ch 2022-08-25 19:31 ` anlauf at gcc dot gnu.org 2022-08-25 19:58 ` [Bug fortran/41453] " anlauf at gcc dot gnu.org 2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org 2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org 2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org 2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org 2022-09-25 16:42 ` mikael at gcc dot gnu.org 2022-09-25 20:32 ` 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-41453-4-GRjMehMSq3@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).