public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vehre at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/100813] Function of array of pointers to abstract class returning an array since r6-202-gf3b0bb7a560be0f0
Date: Wed, 12 Jun 2024 07:23:16 +0000	[thread overview]
Message-ID: <bug-100813-4-ZtskW6D2fQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100813-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100813

Andre Vehreschild <vehre at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |vehre at gcc dot gnu.org
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=104430
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Andre Vehreschild <vehre at gcc dot gnu.org> ---
Reported to be working now. Closing.

      parent reply	other threads:[~2024-06-12  7:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 13:34 [Bug fortran/100813] New: Function of array of pointers to abstract class returning an array mailling-lists-bd at posteo dot de
2021-05-31  8:38 ` [Bug fortran/100813] Function of array of pointers to abstract class returning an array since r6-202-gf3b0bb7a560be0f0 marxin at gcc dot gnu.org
2021-05-31 10:53 ` dominiq at lps dot ens.fr
2022-04-21 18:25 ` mikael at gcc dot gnu.org
2022-04-22 12:31 ` marxin at gcc dot gnu.org
2024-06-12  7:23 ` vehre at gcc dot gnu.org [this message]

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-100813-4-ZtskW6D2fQ@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).