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/102458] New: ICE tree check: expected array_type, have pointer_type in gfc_conv_array_initializer, at fortran/trans-array.c:6136
Date: Wed, 22 Sep 2021 17:42:13 +0000 [thread overview]
Message-ID: <bug-102458-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102458
Bug ID: 102458
Summary: ICE tree check: expected array_type, have pointer_type
in gfc_conv_array_initializer, at
fortran/trans-array.c:6136
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: ---
Affects versions down to at least r5 :
$ cat z1.f90
subroutine s
integer :: a(command_argument_count()) = 1
print *, a
end
$ gfortran-12-20210919 -c z1.f90
z1.f90:1:12:
1 | subroutine s
| 1
internal compiler error: tree check: expected array_type, have pointer_type in
gfc_conv_array_initializer, at fortran/trans-array.c:6136
0x6938d8 tree_check_failed(tree_node const*, char const*, int, char const*,
...)
../../gcc/tree.c:8689
0x7de241 tree_check(tree_node*, char const*, int, char const*, tree_code)
../../gcc/tree.h:3427
0x7de241 gfc_conv_array_initializer(tree_node*, gfc_expr*)
../../gcc/fortran/trans-array.c:6133
0x81f1b0 gfc_conv_initializer(gfc_expr*, gfc_typespec*, tree_node*, bool, bool,
bool)
../../gcc/fortran/trans-expr.c:8014
0x7ff6ca gfc_get_symbol_decl(gfc_symbol*)
../../gcc/fortran/trans-decl.c:1940
0x80324f generate_local_decl
../../gcc/fortran/trans-decl.c:5989
0x7b3592 do_traverse_symtree
../../gcc/fortran/symbol.c:4170
0x80479c generate_local_vars
../../gcc/fortran/trans-decl.c:6195
0x80479c gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6854
0x77be66 translate_all_program_units
../../gcc/fortran/parse.c:6572
0x77be66 gfc_parse_file()
../../gcc/fortran/parse.c:6841
0x7c90df gfc_be_parse_file
../../gcc/fortran/f95-lang.c:216
next reply other threads:[~2021-09-22 17:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 17:42 gscfq@t-online.de [this message]
2021-09-22 17:42 ` [Bug fortran/102458] " gscfq@t-online.de
2021-09-22 19:07 ` anlauf at gcc dot gnu.org
2021-09-22 19:55 ` kargl at gcc dot gnu.org
2021-09-22 20:01 ` anlauf at gcc dot gnu.org
2021-09-22 20:03 ` kargl at gcc dot gnu.org
2021-09-22 20:43 ` anlauf at gcc dot gnu.org
2021-09-22 21:17 ` anlauf at gcc dot gnu.org
2021-09-22 23:18 ` sgk at troutmask dot apl.washington.edu
2021-09-23 19:28 ` anlauf at gcc dot gnu.org
2021-09-23 19:52 ` anlauf at gcc dot gnu.org
2021-09-24 17:11 ` cvs-commit at gcc dot gnu.org
2021-09-27 21:14 ` anlauf at gcc dot gnu.org
2021-09-29 19:22 ` anlauf at gcc dot gnu.org
2021-09-30 18:29 ` cvs-commit at gcc dot gnu.org
2021-10-03 19:34 ` cvs-commit at gcc dot gnu.org
2021-10-03 19:34 ` cvs-commit at gcc dot gnu.org
2021-10-05 19:51 ` cvs-commit at gcc dot gnu.org
2021-10-05 19:51 ` cvs-commit at gcc dot gnu.org
2021-10-05 19:53 ` 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-102458-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).