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/108527] New: [13 Regression] ICE in compare_bound_int(): Bad expression
Date: Tue, 24 Jan 2023 17:51:18 +0000	[thread overview]
Message-ID: <bug-108527-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 108527
           Summary: [13 Regression] ICE in compare_bound_int(): Bad
                    expression
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started between 20221218 and 20230108,
was fixed, but testcases from pr103505 give an ICE again :


$ cat z1.f90
program p
   integer, parameter :: a((2.)) = [4, 8]
   integer(a(1:1)) :: b
end


$ cat z2.f90
program p
   integer, parameter :: a((2.)) = [4, 8]
   print *, [integer(a(1:1)) :: 2]
end


$ cat z3.f90
program p
   integer, parameter :: a((2.)) = [4, 8]
   integer :: b(a(1:1))
end


$ gfortran-13-20230122 -c z1.f90
f951: internal compiler error: compare_bound_int(): Bad expression
0x7c17e9 gfc_report_diagnostic
        ../../gcc/fortran/error.cc:883
0x7c3387 gfc_internal_error(char const*, ...)
        ../../gcc/fortran/error.cc:1503
0x834531 compare_bound_mpz_t
        ../../gcc/fortran/resolve.cc:4605
0x834a7c check_dimension
        ../../gcc/fortran/resolve.cc:4788
0x847ddd compare_spec_to_ref
        ../../gcc/fortran/resolve.cc:4853
0x847ddd resolve_array_ref
        ../../gcc/fortran/resolve.cc:5151
0x847ddd gfc_resolve_ref(gfc_expr*)
        ../../gcc/fortran/resolve.cc:5366
0x837bc7 resolve_variable
        ../../gcc/fortran/resolve.cc:5871
0x837bc7 gfc_resolve_expr(gfc_expr*)
        ../../gcc/fortran/resolve.cc:7197
0x7c77a4 gfc_reduce_init_expr(gfc_expr*)
        ../../gcc/fortran/expr.cc:3168
0x7ca700 gfc_match_init_expr(gfc_expr**)
        ../../gcc/fortran/expr.cc:3216
0x7aa94a gfc_match_kind_spec(gfc_typespec*, bool)
        ../../gcc/fortran/decl.cc:3273
0x7b12e9 gfc_match_decl_type_spec(gfc_typespec*, int)
        ../../gcc/fortran/decl.cc:4706
0x7b2cac gfc_match_data_decl()
        ../../gcc/fortran/decl.cc:6264
0x8215d3 match_word
        ../../gcc/fortran/parse.cc:67
0x8215d3 decode_statement
        ../../gcc/fortran/parse.cc:378
0x82301a next_free
        ../../gcc/fortran/parse.cc:1403
0x82301a next_statement
        ../../gcc/fortran/parse.cc:1635
0x824a5b parse_spec
        ../../gcc/fortran/parse.cc:4191
0x827d5c parse_progunit
        ../../gcc/fortran/parse.cc:6262

             reply	other threads:[~2023-01-24 17:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 17:51 gscfq@t-online.de [this message]
2023-01-24 18:42 ` [Bug fortran/108527] " anlauf at gcc dot gnu.org
2023-01-24 19:02 ` kargl at gcc dot gnu.org
2023-01-24 19:32 ` anlauf at gcc dot gnu.org
2023-01-24 20:51 ` anlauf at gcc dot gnu.org
2023-01-24 20:52 ` sgk at troutmask dot apl.washington.edu
2023-01-24 21:49 ` anlauf at gcc dot gnu.org
2023-01-25  7:36 ` rguenth at gcc dot gnu.org
2023-01-25  9:48 ` marxin at gcc dot gnu.org
2023-01-25 19:29 ` anlauf at gcc dot gnu.org
2023-01-28 21:00 ` cvs-commit at gcc dot gnu.org
2023-02-05 19:28 ` cvs-commit at gcc dot gnu.org
2023-02-10 19:29 ` cvs-commit at gcc dot gnu.org
2023-02-11 18:16 ` cvs-commit at gcc dot gnu.org
2023-02-11 18:18 ` 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-108527-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).