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/50549] should detect different type parameters in structure constructors (r178939) Date: Thu, 24 Mar 2022 21:13:25 +0000 [thread overview] Message-ID: <bug-50549-4-G9c12eZpq2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50549-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50549 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gcc dot gnu.org --- Comment #3 from anlauf at gcc dot gnu.org --- Created attachment 52683 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52683&action=edit Tentative patch This patch provides an error message somewhat similar to NAG, e.g. pr50549.f90:13:6: 13 | u=t(p1) ! different character length | 1 Error: Unequal character lengths (2/1) for pointer component 'p2' in constructor at (1) Regtesting looks fine.
next prev parent reply other threads:[~2022-03-24 21:13 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-28 9:10 [Bug fortran/50549] New: " zeccav at gmail dot com 2013-06-22 15:20 ` [Bug fortran/50549] " dominiq at lps dot ens.fr 2021-02-27 8:27 ` zeccav at gmail dot com 2022-03-24 21:13 ` anlauf at gcc dot gnu.org [this message] 2022-03-27 19:45 ` anlauf at gcc dot gnu.org 2022-03-29 18:36 ` cvs-commit at gcc dot gnu.org 2022-03-29 18:49 ` anlauf 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-50549-4-G9c12eZpq2@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).