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/102715] New: [12 Regression] ICE in gfc_simplify_transpose, at fortran/simplify.c:8184
Date: Tue, 12 Oct 2021 17:31:56 +0000	[thread overview]
Message-ID: <bug-102715-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102715
           Summary: [12 Regression] ICE in gfc_simplify_transpose, at
                    fortran/simplify.c:8184
           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: ---

Changed between 20211003 and 20211010 :
(follow-up of pr102520)


$ cat z1.f90
program p
   type t
   end type
   type(t), parameter :: a(4) = t()
   type(t), parameter :: b(2,2) = reshape(a, [2])
   type(t), parameter :: c(2,2) = transpose(b)
end


$ gfortran-12-20211003 -c z1.f90
z1.f90:5:31:

    5 |    type(t), parameter :: b(2,2) = reshape(a, [2])
      |                               1
Error: Incompatible ranks 2 and 1 in assignment at (1)


$ gfortran-12-20211010 -c z1.f90
f951: internal compiler error: Segmentation fault
0xd43fcf crash_signal
        ../../gcc/toplev.c:326
0x82d8f0 gfc_simplify_transpose(gfc_expr*)
        ../../gcc/fortran/simplify.c:8184
0x7aa66a do_simplify
        ../../gcc/fortran/intrinsic.c:4657
0x7b50ba gfc_intrinsic_func_interface(gfc_expr*, int)
        ../../gcc/fortran/intrinsic.c:5050
0x8078e9 resolve_unknown_f
        ../../gcc/fortran/resolve.c:2937
0x8078e9 resolve_function
        ../../gcc/fortran/resolve.c:3281
0x8078e9 gfc_resolve_expr(gfc_expr*)
        ../../gcc/fortran/resolve.c:7115
0x79a244 gfc_reduce_init_expr(gfc_expr*)
        ../../gcc/fortran/expr.c:3125
0x79d4b0 gfc_match_init_expr(gfc_expr**)
        ../../gcc/fortran/expr.c:3173
0x787c74 variable_decl
        ../../gcc/fortran/decl.c:3016
0x787c74 gfc_match_data_decl()
        ../../gcc/fortran/decl.c:6325
0x7f01d3 match_word
        ../../gcc/fortran/parse.c:65
0x7f01d3 decode_statement
        ../../gcc/fortran/parse.c:376
0x7f1c1a next_free
        ../../gcc/fortran/parse.c:1384
0x7f1c1a next_statement
        ../../gcc/fortran/parse.c:1616
0x7f333b parse_spec
        ../../gcc/fortran/parse.c:4151
0x7f610c parse_progunit
        ../../gcc/fortran/parse.c:6117
0x7f7891 gfc_parse_file()
        ../../gcc/fortran/parse.c:6658
0x84480f gfc_be_parse_file
        ../../gcc/fortran/f95-lang.c:216

             reply	other threads:[~2021-10-12 17:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 17:31 gscfq@t-online.de [this message]
2021-10-13  7:32 ` [Bug fortran/102715] " rguenth at gcc dot gnu.org
2021-10-13  7:32 ` rguenth at gcc dot gnu.org
2021-10-13 12:13 ` [Bug fortran/102715] [12 Regression] ICE in gfc_simplify_transpose, at fortran/simplify.c:8184 since r12-4278-g74ccca380cde5e79 marxin at gcc dot gnu.org
2021-10-31 21:36 ` anlauf at gcc dot gnu.org
2021-11-06 18:44 ` cvs-commit at gcc dot gnu.org
2021-11-07 20:54 ` cvs-commit at gcc dot gnu.org
2021-11-13 20:15 ` cvs-commit at gcc dot gnu.org
2021-11-13 20: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-102715-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).