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/105658] Passing array component to unlimited polymorphic routine passes wrong slice Date: Wed, 06 Mar 2024 21:12:06 +0000 [thread overview] Message-ID: <bug-105658-4-j45fghImfO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105658-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105658 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Priority|P3 |P4 Target Milestone|--- |14.0 Status|NEW |RESOLVED --- Comment #3 from anlauf at gcc dot gnu.org --- Backporting to 13-branch appears to depend on a backport of Paul's commit r14-870-g6c95fe9bc05537, or part of it, plus maybe more. Might be risky. Setting target milestone to 14 and closing. Thanks to Peter for the patch!
prev parent reply other threads:[~2024-03-06 21:12 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-19 9:28 [Bug fortran/105658] New: " zed.three at gmail dot com 2024-02-20 19:50 ` [Bug fortran/105658] " cvs-commit at gcc dot gnu.org 2024-02-20 19:57 ` anlauf at gcc dot gnu.org 2024-03-06 21:12 ` 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-105658-4-j45fghImfO@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).