public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/97045] A wrong column is selected when addressing individual elements of unlimited polymorphic dummy argument Date: Sun, 20 Sep 2020 16:57:36 +0000 [thread overview] Message-ID: <bug-97045-4-1nXrrNGBTt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97045-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97045 Paul Thomas <pault at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pault at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed| |2020-09-20 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Paul Thomas <pault at gcc dot gnu.org> --- Created attachment 49244 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49244&action=edit Patch for the PR Thanks for posting on Bugzilla, Igor. It makes the workflow much easier. The attached fixes the problem and regtests OK. The first part of the patch does not affect your testcase since it only has effect for character selectors. I'll be some days before I get to submit this because I have a bit of a backlog. Regards Paul
next prev parent reply other threads:[~2020-09-20 16:57 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-14 14:45 [Bug fortran/97045] New: " igor.gayday at mu dot edu 2020-09-20 16:57 ` pault at gcc dot gnu.org [this message] 2020-09-25 15:34 ` [Bug fortran/97045] " pault at gcc dot gnu.org 2020-09-30 12:44 ` cvs-commit at gcc dot gnu.org 2023-10-30 19:42 ` anlauf at gcc dot gnu.org 2023-10-31 7:32 ` pault 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-97045-4-1nXrrNGBTt@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).