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/112834] New: Class array function selector causes chain of syntax and other spurious errors Date: Sun, 03 Dec 2023 17:56:32 +0000 [thread overview] Message-ID: <bug-112834-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112834 Bug ID: 112834 Summary: Class array function selector causes chain of syntax and other spurious errors Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: pault at gcc dot gnu.org Target Milestone: --- Created attachment 56777 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56777&action=edit testcase demonstrating problem The attached produces: [pault@pc30 pr87477]$ rm ./a.out;~/grun/bin/gfortran test.f90 -fdump-tree-original -g;./a.out test.f90:24:15: 24 | if (var1(2)%i .ne. test_array(2)%i) stop 9 | 1 Error: Syntax error in IF-expression at (1) test.f90:31:16: 31 | if (x(1)%i .ne. test_array(1)%i) stop 11 | 1 Error: Syntax error in IF-expression at (1) test.f90:39:52: 39 | print *, "yes, size of 'y' is ", size(y), y(1) | 1 Error: Syntax error in PRINT statement at (1) test.f90:44:26: 44 | end module class_selectors | 1 Error: Pointer assignment target in initialization expression does not have the TARGET attribute at (1) test.f90:46:7: 46 | use class_selectors | 1 Fatal Error: Cannot open module file ‘class_selectors.mod’ for reading at (1): No such file or directory compilation terminated Paul
next reply other threads:[~2023-12-03 17:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-03 17:56 pault at gcc dot gnu.org [this message] 2023-12-06 12:31 ` [Bug fortran/112834] " pault at gcc dot gnu.org 2023-12-06 12:33 ` pault at gcc dot gnu.org 2023-12-16 13:27 ` cvs-commit at gcc dot gnu.org 2024-03-06 15:19 ` 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-112834-4@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).