public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/51605] internal compiler error gfc_trans_block_construct, at fortran/trans-stmt.c:984 Date: Mon, 06 Mar 2023 17:18:34 +0000 [thread overview] Message-ID: <bug-51605-4-shAyzbtaWk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51605-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51605 Bug 51605 depends on bug 51610, which changed state. Bug 51610 Summary: [OOP] Class container does not properly handle POINTER and TARGET https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51610 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE
prev parent reply other threads:[~2023-03-06 17:18 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-17 22:46 [Bug fortran/51605] New: " danlnagle at me dot com 2011-12-17 23:26 ` [Bug fortran/51605] " danlnagle at me dot com 2011-12-17 23:48 ` dominiq at lps dot ens.fr 2011-12-18 9:24 ` kargl at gcc dot gnu.org 2011-12-18 10:08 ` burnus at gcc dot gnu.org 2011-12-18 13:55 ` danlnagle at me dot com 2011-12-18 14:15 ` burnus at gcc dot gnu.org 2011-12-18 16:57 ` sgk at troutmask dot apl.washington.edu 2011-12-19 11:52 ` burnus at gcc dot gnu.org 2011-12-19 13:19 ` burnus at gcc dot gnu.org 2011-12-19 15:32 ` burnus at gcc dot gnu.org 2011-12-19 15:54 ` danlnagle at me dot com 2011-12-19 18:56 ` burnus at gcc dot gnu.org 2011-12-19 20:26 ` burnus at gcc dot gnu.org 2011-12-19 20:30 ` burnus at gcc dot gnu.org 2013-12-14 20:15 ` dominiq at lps dot ens.fr 2013-12-14 22:25 ` janus at gcc dot gnu.org 2023-03-06 17:18 ` anlauf 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-51605-4-shAyzbtaWk@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).