public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95037] gfortran fails to compile a simple subroutine, issues an opaque message
Date: Sun, 14 Jun 2020 12:45:46 +0000 [thread overview]
Message-ID: <bug-95037-4-wbhGRGrozd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95037-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95037
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed on master with
https://gcc.gnu.org/g:4644e8f15f835a9934a8d289ee08ba4cb46cbfac
commit r11-1297-g4644e8f15f835a9934a8d289ee08ba4cb46cbfac
Author: Thomas Koenig <tkoenig@gcc.gnu.org>
Date: Sun Jun 14 14:39:03 2020 +0200
Always use locations from get and put arguments for error messages.
A simple and obvios patch - the error location was taken
from a variable that was not initialized for optional
variables.
gcc/fortran/ChangeLog:
* check.c (gfc_check_random_seed): Always use locations
from get and put arguments for error messages.
gcc/testsuite/ChangeLog:
* gfortran.dg/random_seed_4.f90: New test.
Closing. Thanks for the bug report!
next prev parent reply other threads:[~2020-06-14 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 15:35 [Bug fortran/95037] New: " longb at cray dot com
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 [this message]
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-wbhGRGrozd@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: link
Be 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).