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/114827] Valgrind reports errors with class(*) assignment Date: Thu, 09 May 2024 18:30:15 +0000 [thread overview] Message-ID: <bug-114827-4-SFGhHAngww@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114827-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114827 --- Comment #13 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-14 branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:a5046235509caa10a4dc309ca0a8e67892b27750 commit r14-10191-ga5046235509caa10a4dc309ca0a8e67892b27750 Author: Harald Anlauf <anlauf@gmx.de> Date: Mon Apr 29 19:52:52 2024 +0200 Fortran: fix issues with class(*) assignment [PR114827] gcc/fortran/ChangeLog: PR fortran/114827 * trans-array.cc (gfc_alloc_allocatable_for_assignment): Take into account _len of unlimited polymorphic entities when calculating the effective element size for allocation size and array span. Set _len of lhs to _len of rhs. * trans-expr.cc (trans_class_assignment): Take into account _len of unlimited polymorphic entities for allocation size. gcc/testsuite/ChangeLog: PR fortran/114827 * gfortran.dg/asan/unlimited_polymorphic_34.f90: New test. (cherry picked from commit 21e7aa5f3ea44ca2fef8deb8788edffc04901b5c)
next prev parent reply other threads:[~2024-05-09 18:30 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-23 17:22 [Bug fortran/114827] New: " neil.n.carlson at gmail dot com 2024-04-23 17:24 ` [Bug fortran/114827] " neil.n.carlson at gmail dot com 2024-04-24 3:16 ` jvdelisle at gcc dot gnu.org 2024-04-24 13:19 ` neil.n.carlson at gmail dot com 2024-04-24 15:07 ` neil.n.carlson at gmail dot com 2024-04-24 19:47 ` anlauf at gcc dot gnu.org 2024-04-25 18:43 ` neil.n.carlson at gmail dot com 2024-04-26 19:33 ` anlauf at gcc dot gnu.org 2024-04-27 19:44 ` anlauf at gcc dot gnu.org 2024-04-28 20:37 ` anlauf at gcc dot gnu.org 2024-04-28 22:37 ` neil.n.carlson at gmail dot com 2024-04-29 18:39 ` anlauf at gcc dot gnu.org 2024-05-05 18:35 ` cvs-commit at gcc dot gnu.org 2024-05-09 18:30 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-21 19:16 ` anlauf at gcc dot gnu.org 2024-05-22 18:49 ` cvs-commit at gcc dot gnu.org 2024-05-22 18:55 ` 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-114827-4-SFGhHAngww@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).