public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikael Morin <mikael@gcc.gnu.org>
To: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [PATCH v3 0/2] fortran: Fix specification checks [PR111781]
Date: Tue, 19 Mar 2024 16:49:14 +0100	[thread overview]
Message-ID: <20240319154918.272178-1-mikael@gcc.gnu.org> (raw)

Hello,

these patches correct diagnostics dealing with variables in specification
expressions.
The first patch is a testsuite change, which fixes invalid specification
expressions that the second patch would diagnose.
The second patch removes a spurious diagnostic when a dummy procedure is
involved, and enables more valid ones, as visible in the testcases from the
first patch.

I haven't tested it again (same code as v2), but I plan to do it before the final push.
Ok for master?

Mikael

v2 -> v3 changes:

  - Correct first name in testcase comment
  - Clarify and correct log and changelog text from second patch
  - Target current stage (stage4) instead of next (stage1)

v1 -> v2 changes:

  - Fix condition guarding sym->result access.

 
Mikael Morin (2):
  testsuite: Declare fortran array bound variables
  fortran: Fix specification expression error with dummy procedures
    [PR111781]

 gcc/fortran/expr.cc                           |  8 +-
 gcc/fortran/gfortran.h                        |  4 +-
 gcc/fortran/resolve.cc                        | 77 +++++++++----------
 gcc/fortran/symbol.cc                         | 58 ++++++++++++++
 .../gfortran.dg/graphite/pr107865.f90         |  2 +-
 gcc/testsuite/gfortran.dg/pr101267.f90        |  2 +-
 gcc/testsuite/gfortran.dg/pr112404.f90        |  2 +-
 gcc/testsuite/gfortran.dg/pr78061.f           |  2 +-
 gcc/testsuite/gfortran.dg/pr79315.f90         |  6 +-
 gcc/testsuite/gfortran.dg/spec_expr_8.f90     | 24 ++++++
 gcc/testsuite/gfortran.dg/spec_expr_9.f90     | 19 +++++
 gcc/testsuite/gfortran.dg/vect/pr90681.f      |  2 +-
 gcc/testsuite/gfortran.dg/vect/pr97761.f90    |  2 +-
 gcc/testsuite/gfortran.dg/vect/pr99746.f90    |  2 +-
 14 files changed, 152 insertions(+), 58 deletions(-)
 create mode 100644 gcc/testsuite/gfortran.dg/spec_expr_8.f90
 create mode 100644 gcc/testsuite/gfortran.dg/spec_expr_9.f90

-- 
2.43.0


             reply	other threads:[~2024-03-19 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 15:49 Mikael Morin [this message]
2024-03-19 15:49 ` [PATCH v3 1/2] testsuite: Declare fortran array bound variables Mikael Morin
2024-03-19 17:25   ` Paul Richard Thomas
2024-03-19 15:49 ` [PATCH v3 2/2] fortran: Fix specification expression error with dummy procedures [PR111781] Mikael Morin
2024-03-19 17:33   ` Paul Richard Thomas
2024-03-19 17:27 ` [PATCH v3 0/2] fortran: Fix specification checks [PR111781] Paul Richard Thomas

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=20240319154918.272178-1-mikael@gcc.gnu.org \
    --to=mikael@gcc.gnu.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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).