From: Mark Eggleston <mark.eggleston@codethink.co.uk>
To: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: [Regression, patch][Fortran] ICE in gfc_conv_constant_to_tree PR93604
Date: Mon, 24 Feb 2020 12:05:00 -0000 [thread overview]
Message-ID: <33d27a88-6d38-1476-f90c-7d913be8d077@codethink.co.uk> (raw)
In-Reply-To: <1c85a4a2-75ca-e06f-ced2-cdd97c7de9cf@codethink.co.uk>
**ping**
On 17/02/2020 11:26, Mark Eggleston wrote:
> Please find attached patch for PR93604.
>
> gcc/fortran/ChangeLog
>
>    Steven G. Kargl <kargl@gcc.gnu.org>
>
> Â Â Â PR fortran/93604
> Â Â Â * decl.c (gfc_match_data) : Check whether the data expression
> Â Â Â is a derived type and is a constructor. If a BOZ constant
> Â Â Â is encountered in the constructor output an error and return
> Â Â Â MATCH_ERROR.
>
> gcc/testsuite/ChangeLog
>
>    Mark Eggleston <mark.eggleston@codethink.com>
>
> Â Â Â PR fortran/93604
> Â Â Â * gfortran.dg/pr93604.f90 : New test.
>
> OK to commit?
>
--
https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2020-02-24 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 11:26 Mark Eggleston
2020-02-24 12:05 ` Mark Eggleston [this message]
2020-02-24 13:30 ` Thomas Koenig
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=33d27a88-6d38-1476-f90c-7d913be8d077@codethink.co.uk \
--to=mark.eggleston@codethink.co.uk \
--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).