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/90076] Polymorphic Allocate on Assignment Memory Leak Date: Wed, 19 Jun 2024 09:29:04 +0000 [thread overview] Message-ID: <bug-90076-4-m6FNrregpX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-90076-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90076 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andre Vehreschild <vehre@gcc.gnu.org>: https://gcc.gnu.org/g:dbb718175d7df89b957b316ba2f5fbea5d21b2b1 commit r15-1434-gdbb718175d7df89b957b316ba2f5fbea5d21b2b1 Author: Andre Vehreschild <vehre@gcc.gnu.org> Date: Thu Jun 6 14:01:13 2024 +0200 Fortran: Set the vptr of a class typed result. PR fortran/90076 gcc/fortran/ChangeLog: * trans-decl.cc (gfc_generate_function_code): Set vptr for results to declared class type. * trans-expr.cc (gfc_reset_vptr): Allow to provide the typespec instead of the expression. * trans.h (gfc_reset_vptr): Same. gcc/testsuite/ChangeLog: * gfortran.dg/class_76.f90: Add declared vtab occurrence. * gfortran.dg/class_78.f90: New test.
next prev parent reply other threads:[~2024-06-19 9:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-90076-4@http.gcc.gnu.org/bugzilla/> 2024-06-11 12:57 ` vehre at gcc dot gnu.org 2024-06-11 12:58 ` vehre at gcc dot gnu.org 2024-06-11 12:59 ` vehre at gcc dot gnu.org 2024-06-19 9:29 ` cvs-commit at gcc dot gnu.org [this message] 2024-06-19 9:43 ` vehre 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-90076-4-m6FNrregpX@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).