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/100098] Polymorphic pointers and allocatables have incorrect rank Date: Sat, 29 Oct 2022 20:21:59 +0000 [thread overview] Message-ID: <bug-100098-4-wfVdBFyzAv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100098-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100098 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:2b20cf18a62842e2659e891b0c607769638e07f9 commit r12-8877-g2b20cf18a62842e2659e891b0c607769638e07f9 Author: José Rui Faustino de Sousa <jrfsousa@gmail.com> Date: Tue Oct 18 22:29:59 2022 +0200 Fortran: Add missing TKR initialization to class variables [PR100097, PR100098] gcc/fortran/ChangeLog: PR fortran/100097 PR fortran/100098 * trans-array.cc (gfc_trans_class_array): New function to initialize class descriptor's TKR information. * trans-array.h (gfc_trans_class_array): Add function prototype. * trans-decl.cc (gfc_trans_deferred_vars): Add calls to the new function for both pointers and allocatables. gcc/testsuite/ChangeLog: PR fortran/100097 PR fortran/100098 * gfortran.dg/PR100097.f90: New test. * gfortran.dg/PR100098.f90: New test. (cherry picked from commit 4cfdaeb2755121ac1069f09898def56469b0fb51)
next prev parent reply other threads:[~2022-10-29 20:21 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-15 12:46 [Bug fortran/100098] New: " jrfsousa at gmail dot com 2021-04-16 13:38 ` [Bug fortran/100098] " dominiq at lps dot ens.fr 2021-04-16 23:20 ` jrfsousa at gmail dot com 2022-10-18 20:44 ` anlauf at gcc dot gnu.org 2022-10-21 18:19 ` cvs-commit at gcc dot gnu.org 2022-10-29 20:21 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-29 20:25 ` cvs-commit at gcc dot gnu.org 2022-10-29 20:26 ` 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-100098-4-wfVdBFyzAv@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).