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/100948] New: [12 Regression] ICE in gfc_conv_expr_val, at fortran/trans-expr.c:9069
Date: Mon, 07 Jun 2021 17:31:26 +0000	[thread overview]
Message-ID: <bug-100948-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 100948
           Summary: [12 Regression] ICE in gfc_conv_expr_val, at
                    fortran/trans-expr.c:9069
           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: ---

This changed between 20210530 (accepted) and 20210606 (ICE) :
(see also pr83522)


$ cat z1.f90
program p
   type t
      character(:), allocatable :: c(:)
   end type
   type(t), allocatable :: x
   associate (y => x%c(:)(:))
   end associate
end


$ gfortran-12-20210530 -c z1.f90
$
$ gfortran-12-20210606 -c z1.f90
z1.f90:6:29:

    6 |    associate (y => x%c(:)(:))
      |                             1
internal compiler error: Segmentation fault
0xc79a6f crash_signal
        ../../gcc/toplev.c:327
0x7cf4f6 gfc_conv_expr_val(gfc_se*, gfc_expr*)
        ../../gcc/fortran/trans-expr.c:9069
0x7cf723 gfc_conv_expr_type(gfc_se*, gfc_expr*, tree_node*)
        ../../gcc/fortran/trans-expr.c:9084
0x7cf723 gfc_get_expr_charlen(gfc_expr*)
        ../../gcc/fortran/trans-expr.c:2158
0x7a11bf gfc_get_array_span(tree_node*, gfc_expr*)
        ../../gcc/fortran/trans-array.c:873
0x7acab0 gfc_conv_expr_descriptor(gfc_se*, gfc_expr*)
        ../../gcc/fortran/trans-array.c:7740
0x80d462 trans_associate_var
        ../../gcc/fortran/trans-stmt.c:1917
0x8141f1 gfc_trans_block_construct(gfc_code*)
        ../../gcc/fortran/trans-stmt.c:2311
0x79e5a7 trans_code
        ../../gcc/fortran/trans.c:2014
0x7c4bc4 gfc_generate_function_code(gfc_namespace*)
        ../../gcc/fortran/trans-decl.c:6893
0x74b3f6 translate_all_program_units
        ../../gcc/fortran/parse.c:6461
0x74b3f6 gfc_parse_file()
        ../../gcc/fortran/parse.c:6730
0x79772f gfc_be_parse_file
        ../../gcc/fortran/f95-lang.c:212

             reply	other threads:[~2021-06-07 17:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 17:31 gscfq@t-online.de [this message]
2021-06-07 18:02 ` [Bug fortran/100948] " gscfq@t-online.de
2021-06-07 19:34 ` anlauf at gcc dot gnu.org
2021-06-07 19:36 ` anlauf at gcc dot gnu.org
2021-06-11 12:37 ` marxin at gcc dot gnu.org
2021-06-11 15:33 ` jrfsousa at gcc dot gnu.org
2021-06-13 19:15 ` jrfsousa at gcc dot gnu.org
2021-06-13 19:16 ` jrfsousa at gcc dot gnu.org
2022-01-17 14:37 ` rguenth at gcc dot gnu.org
2022-05-06  8:30 ` [Bug fortran/100948] [12/13 " jakub at gcc dot gnu.org
2023-04-08  8:04 ` cvs-commit at gcc dot gnu.org
2023-04-08  9:33 ` pault 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-100948-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).