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/98022] [9/10/11 Regression] ICE in gfc_assign_data_value, at fortran/data.c:468 since r9-3803-ga5fbc2f36a291cbe
Date: Sat, 26 Dec 2020 16:44:40 +0000	[thread overview]
Message-ID: <bug-98022-4-7My5d7dk5p@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98022-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Paul Thomas <pault@gcc.gnu.org>:

https://gcc.gnu.org/g:c7256c8260afa313e019fd531574ad33ec49b9f6

commit r11-6342-gc7256c8260afa313e019fd531574ad33ec49b9f6
Author: Paul Thomas <pault@gcc.gnu.org>
Date:   Sat Dec 26 16:44:24 2020 +0000

    Fortran: Correction to recent patch in light of comments [PR98022].

    2020-12-26  Paul Thomas  <pault@gcc.gnu.org>

    gcc/fortran
            PR fortran/98022
            * data.c (gfc_assign_data_value): Throw an error for inquiry
            references. Follow with corrected code that would provide the
            expected result and provides clean error recovery.

    gcc/testsuite/
            PR fortran/98022
            * gfortran.dg/data_inquiry_ref.f90: Change to dg-compile and
            add errors for inquiry references.

  parent reply	other threads:[~2020-12-26 16:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27  3:22 [Bug fortran/98022] New: ICE in gfc_assign_data_value, at fortran/data.c:468 asolokha at gmx dot com
2020-11-27 11:18 ` [Bug fortran/98022] [9/10/11 Regression] ICE in gfc_assign_data_value, at fortran/data.c:468 since r9-3803-ga5fbc2f36a291cbe marxin at gcc dot gnu.org
2020-11-27 11:26 ` pault at gcc dot gnu.org
2020-12-09 17:25 ` pault at gcc dot gnu.org
2020-12-09 18:13 ` kargl at gcc dot gnu.org
2020-12-12 14:01 ` cvs-commit at gcc dot gnu.org
2020-12-12 16:02 ` pault at gcc dot gnu.org
2020-12-12 16:34 ` sgk at troutmask dot apl.washington.edu
2020-12-12 17:54 ` pault at gcc dot gnu.org
2020-12-12 18:24 ` sgk at troutmask dot apl.washington.edu
2020-12-26 16:44 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-23 10:37 ` cvs-commit at gcc dot gnu.org
2021-01-23 10:43 ` cvs-commit at gcc dot gnu.org
2021-01-23 10:44 ` cvs-commit at gcc dot gnu.org
2021-01-23 10:44 ` cvs-commit at gcc dot gnu.org
2021-01-27 11:21 ` 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-98022-4-7My5d7dk5p@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).