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/102275] Assumed rank, unlimited polymorphic pointer gives incorrect behaviour Date: Sun, 09 Oct 2022 18:24:21 +0000 [thread overview] Message-ID: <bug-102275-4-lEN2KhrMK8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102275-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102275 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |10.4.0, 11.2.0, 11.3.0 Keywords| |wrong-code Known to work| |12.2.1, 13.0 --- Comment #2 from anlauf at gcc dot gnu.org --- Adding versions known to work and known to fail.
prev parent reply other threads:[~2022-10-09 18:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-10 13:18 [Bug fortran/102275] New: Assumed rank, unlimited polymorphic pointer gives incorrect behavious paal at levold dot net 2022-10-08 20:41 ` [Bug fortran/102275] Assumed rank, unlimited polymorphic pointer gives incorrect behaviour mikael at gcc dot gnu.org 2022-10-09 18:24 ` 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-102275-4-lEN2KhrMK8@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).