public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/100972] Missing error with "implicit none (external)"
Date: Fri, 05 Nov 2021 21:10:12 +0000	[thread overview]
Message-ID: <bug-100972-4-Qw4SGsFAJm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100972-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100972

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Bernhard Reutner-Fischer
<aldot@gcc.gnu.org>:

https://gcc.gnu.org/g:1727bb533ede295a3ef2dd494225d27b6d1746aa

commit r12-4961-g1727bb533ede295a3ef2dd494225d27b6d1746aa
Author: Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
Date:   Sun Oct 31 17:44:45 2021 +0100

    Fortran: Missing error with IMPLICIT none (external) [PR100972]

    gcc/fortran/ChangeLog:

            PR fortran/100972
            * decl.c (gfc_match_implicit_none): Fix typo in warning.
            * resolve.c (resolve_unknown_f): Reject external procedures
            without explicit EXTERNAL attribute whe IMPLICIT none (external)
            is in effect.

    gcc/testsuite/ChangeLog:

            PR fortran/100972
            * gfortran.dg/implicit_14.f90: Adjust error.
            * gfortran.dg/external_implicit_none_3.f08: New test.

  parent reply	other threads:[~2021-11-05 21:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 17:17 [Bug fortran/100972] New: " gscfq@t-online.de
2021-06-09 16:30 ` [Bug fortran/100972] " gscfq@t-online.de
2021-10-31 17:36 ` aldot at gcc dot gnu.org
2021-11-05 21:10 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-15  7:36 ` aldot at gcc dot gnu.org
2022-11-28 22:20 ` pinskia 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-100972-4-Qw4SGsFAJm@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).