public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/103412] New: [10/11/12 Regression] ICE: Invalid expression in gfc_element_size
Date: Wed, 24 Nov 2021 17:45:10 +0000	[thread overview]
Message-ID: <bug-103412-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103412
           Summary: [10/11/12 Regression] ICE: Invalid expression in
                    gfc_element_size
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started with r10, between 20190630 and 20190728 :
(a few small remnants of the BOZ revision)


$ cat z1.f90
program p
   integer, parameter :: a = sizeof(z'1')
end


$ gfortran-12-20211121 -c z1.f90
f951: internal compiler error: Invalid expression in gfc_element_size.
0x796be9 gfc_report_diagnostic
        ../../gcc/fortran/error.c:874
0x798757 gfc_internal_error(char const*, ...)
        ../../gcc/fortran/error.c:1494
0x83c8f2 gfc_element_size(gfc_expr*, unsigned long*)
        ../../gcc/fortran/target-memory.c:137
0x83c953 gfc_target_expr_size(gfc_expr*, unsigned long*)
        ../../gcc/fortran/target-memory.c:166
0x83086b gfc_simplify_sizeof(gfc_expr*)
        ../../gcc/fortran/simplify.c:7608
0x7ac972 do_simplify
        ../../gcc/fortran/intrinsic.c:4641
0x7b7a7a gfc_intrinsic_func_interface(gfc_expr*, int)
        ../../gcc/fortran/intrinsic.c:5034
0x80b71c resolve_unknown_f
        ../../gcc/fortran/resolve.c:2972
0x80b71c resolve_function
        ../../gcc/fortran/resolve.c:3329
0x80b71c gfc_resolve_expr(gfc_expr*)
        ../../gcc/fortran/resolve.c:7166
0x79cac4 gfc_reduce_init_expr(gfc_expr*)
        ../../gcc/fortran/expr.c:3130
0x79f990 gfc_match_init_expr(gfc_expr**)
        ../../gcc/fortran/expr.c:3178
0x789f44 variable_decl
        ../../gcc/fortran/decl.c:3004
0x789f44 gfc_match_data_decl()
        ../../gcc/fortran/decl.c:6297
0x7f3df3 match_word
        ../../gcc/fortran/parse.c:67
0x7f3df3 decode_statement
        ../../gcc/fortran/parse.c:378
0x7f583a next_free
        ../../gcc/fortran/parse.c:1397
0x7f583a next_statement
        ../../gcc/fortran/parse.c:1629
0x7f7ca4 parse_spec
        ../../gcc/fortran/parse.c:3984
0x7fa2bc parse_progunit
        ../../gcc/fortran/parse.c:6179

             reply	other threads:[~2021-11-24 17:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 17:45 gscfq@t-online.de [this message]
2021-11-24 17:59 ` [Bug fortran/103412] " kargl at gcc dot gnu.org
2021-11-25  7:17 ` rguenth at gcc dot gnu.org
2021-11-25  9:53 ` [Bug fortran/103412] [10/11/12 Regression] ICE: Invalid expression in gfc_element_size since r10-2083-g8dc63166e0b85954 marxin at gcc dot gnu.org
2021-11-25 15:54 ` kargl at gcc dot gnu.org
2021-12-17 21:07 ` anlauf at gcc dot gnu.org
2021-12-17 22:18 ` sgk at troutmask dot apl.washington.edu
2021-12-18 22:22 ` cvs-commit at gcc dot gnu.org
2021-12-18 22:30 ` anlauf at gcc dot gnu.org
2021-12-19 20:05 ` cvs-commit at gcc dot gnu.org
2021-12-19 20:10 ` cvs-commit at gcc dot gnu.org
2021-12-19 20:11 ` 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-103412-4@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).