public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/103413] [10/11/12 Regression] ICE: Invalid expression in gfc_element_size
Date: Wed, 24 Nov 2021 18:15:18 +0000	[thread overview]
Message-ID: <bug-103413-4-Ige3OIK3qN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103413-4@http.gcc.gnu.org/bugzilla/>

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

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2021-11-24
             Status|UNCONFIRMED                 |NEW
           Priority|P3                          |P4
                 CC|                            |kargl at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from kargl at gcc dot gnu.org ---
diff --git a/gcc/fortran/match.c b/gcc/fortran/match.c
index 2bf21434a42..971c2fa1dd6 100644
--- a/gcc/fortran/match.c
+++ b/gcc/fortran/match.c
@@ -4447,6 +4447,15 @@ alloc_opt_list:
              goto cleanup;
            }

+         /* A BOZ cannot be a source expression.  */
+         if (ts.type != BT_BOZ)
+           {
+             gfc_error ("boz-literal-constant cannot be a source expression "
+                        "at %L", &tmp->where);
+             goto cleanup;
+           }
+
+
          /* The next 2 conditionals check C631.  */
          if (ts.type != BT_UNKNOWN)
            {
@@ -4484,6 +4493,14 @@ alloc_opt_list:
              goto cleanup;
            }

+         /* A BOZ cannot be a source expression.  */
+         if (ts.type != BT_BOZ)
+           {
+             gfc_error ("boz-literal-constant cannot be a mode expression "
+                        "at %L", &tmp->where);
+             goto cleanup;
+           }
+
          /* Check F08:C637.  */
          if (ts.type != BT_UNKNOWN)
            {

  reply	other threads:[~2021-11-24 18:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 17:46 [Bug fortran/103413] New: " gscfq@t-online.de
2021-11-24 18:15 ` kargl at gcc dot gnu.org [this message]
2021-11-24 23:21 ` [Bug fortran/103413] " kargl at gcc dot gnu.org
2021-11-25  7:17 ` rguenth at gcc dot gnu.org
2021-11-25  9:55 ` [Bug fortran/103413] [10/11/12 Regression] ICE: Invalid expression in gfc_element_size since r10-2083-g8dc63166e0b85954 marxin at gcc dot gnu.org
2022-06-28 10:47 ` [Bug fortran/103413] [10/11/12/13 " jakub at gcc dot gnu.org
2022-06-28 14:55 ` kargl at gcc dot gnu.org
2022-06-29  8:11 ` marxin at gcc dot gnu.org
2022-06-29 14:46 ` sgk at troutmask dot apl.washington.edu
2022-06-30 12:07 ` marxin at gcc dot gnu.org
2022-10-25 20:22 ` anlauf at gcc dot gnu.org
2022-10-25 21:44 ` kargl at gcc dot gnu.org
2022-10-26 18:24 ` anlauf at gcc dot gnu.org
2022-10-26 19:05 ` sgk at troutmask dot apl.washington.edu
2022-10-26 19:21 ` anlauf at gcc dot gnu.org
2022-10-26 19:22 ` anlauf at gcc dot gnu.org
2022-10-26 20:30 ` sgk at troutmask dot apl.washington.edu
2022-10-26 20:31 ` cvs-commit at gcc dot gnu.org
2022-10-28 20:38 ` cvs-commit at gcc dot gnu.org
2022-10-28 20:48 ` cvs-commit at gcc dot gnu.org
2022-10-28 20:57 ` cvs-commit at gcc dot gnu.org
2022-10-28 20:58 ` anlauf 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-103413-4-Ige3OIK3qN@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).