public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "longb at cray dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/95037] New: gfortran fails to compile a simple subroutine, issues an opaque message Date: Sun, 10 May 2020 15:35:16 +0000 [thread overview] Message-ID: <bug-95037-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95037 Bug ID: 95037 Summary: gfortran fails to compile a simple subroutine, issues an opaque message Product: gcc Version: 9.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: longb at cray dot com Target Milestone: --- > cat test.f90 subroutine my_random_seed_v (size, put, get) integer, optional :: size integer, optional :: put(1) integer, optional :: get(1) call random_seed (size, put, get) end subroutine my_random_seed_v Works with Cray compiler: > ftn -c test.f90 > module swap PrgEnv-cray PrgEnv-gnu Fails with gfortran: > gfortran -c test.f90 (null):0: confused by earlier errors, bailing out > gfortran --version GNU Fortran (GCC) 9.3.0 20200312 (Cray Inc.) Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Original user was "confused" by the message, especially since there were no "earlier errors" output.
next reply other threads:[~2020-05-10 15:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-10 15:35 longb at cray dot com [this message] 2020-05-10 17:29 ` [Bug fortran/95037] " kargl at gcc dot gnu.org 2020-06-14 12:36 ` tkoenig at gcc dot gnu.org 2020-06-14 12:45 ` tkoenig at gcc dot gnu.org 2020-10-18 20:27 ` longb at cray dot com 2020-10-19 5:38 ` tkoenig 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-95037-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).