public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matthew.thompson at nasa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/110415] (Re)allocation on assignment to allocatable polymorphic variable from allocatable polymorphic function result
Date: Mon, 30 Oct 2023 20:05:54 +0000 [thread overview]
Message-ID: <bug-110415-4-zGJG1VYMSb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110415-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110415
Matt Thompson <matthew.thompson at nasa dot gov> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matthew.thompson at nasa dot gov
--- Comment #2 from Matt Thompson <matthew.thompson at nasa dot gov> ---
I was about to file a bug, but I was pointed to search for bug by Brad
Richardon and...yep, this is the one we hit. We found it in one of our base
layers, yaFyaml:
https://github.com/Goddard-Fortran-Ecosystem/yaFyaml
but it's a paradigm we use in codes that use this as well, so...
Thus, +1 from me and I can confirm this is still a bug in 13.2.0. I haven't
tried GNU 14, but I'm guessing since this is still at "NEW" it would be an
issue there as well.
next prev parent reply other threads:[~2023-10-30 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 15:47 [Bug fortran/110415] New: " everythingfunctional at protonmail dot com
2023-06-26 17:21 ` [Bug fortran/110415] " kargl at gcc dot gnu.org
2023-10-30 20:05 ` matthew.thompson at nasa dot gov [this message]
2023-11-20 14:07 ` burnus at gcc dot gnu.org
2023-11-28 15:28 ` cvs-commit at gcc dot gnu.org
2023-11-28 15:39 ` andrewjenner at gcc dot gnu.org
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:52 ` 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-110415-4-zGJG1VYMSb@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: link
Be 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).