public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zeccav at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/80774] [8/9/10/11 Regression][Coarray] ICE in gfc_conv_descriptor_data_get, at fortran/trans-array.c
Date: Sat, 27 Feb 2021 10:02:01 +0000 [thread overview]
Message-ID: <bug-80774-4-DoViyTlVJc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-80774-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80774
--- Comment #6 from Vittorio Zecca <zeccav at gmail dot com> ---
Still in current trunk.
gfortran -S gfbug132.f -fcoarray=single
gfbug132.f:18:72:
18 | deallocate(obj%link)
|
1
internal compiler error: in gfc_get_descriptor_field, at
fortran/trans-array.c:140
0x623c3e gfc_get_descriptor_field
../../gcc-150221/gcc/fortran/trans-array.c:140
0x90990a gfc_conv_descriptor_data_get(tree_node*)
../../gcc-150221/gcc/fortran/trans-array.c:159
0x9078a4 gfc_deallocate_with_status(tree_node*, tree_node*, tree_node*,
tree_node*, tree_node*, bool, gfc_expr*, int, tree_node*, tree_node*)
../../gcc-150221/gcc/fortran/trans.c:1433
0x91bcad structure_alloc_comps
../../gcc-150221/gcc/fortran/trans-array.c:9031
0x91c93a gfc_deallocate_alloc_comp(gfc_symbol*, tree_node*, int, int)
../../gcc-150221/gcc/fortran/trans-array.c:9821
0x908132 gfc_deallocate_scalar_with_status(tree_node*, tree_node*, tree_node*,
bool, gfc_expr*, gfc_typespec, bool)
../../gcc-150221/gcc/fortran/trans.c:1652
0x992c69 gfc_trans_deallocate(gfc_code*)
../../gcc-150221/gcc/fortran/trans-stmt.c:7379
0x9042a7 trans_code
../../gcc-150221/gcc/fortran/trans.c:2098
0x932f53 gfc_generate_function_code(gfc_namespace*)
../../gcc-150221/gcc/fortran/trans-decl.c:6880
0x8afaae translate_all_program_units
../../gcc-150221/gcc/fortran/parse.c:6351
0x8afaae gfc_parse_file()
../../gcc-150221/gcc/fortran/parse.c:6620
0x9010ef gfc_be_parse_file
../../gcc-150221/gcc/fortran/f95-lang.c:212
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
next parent reply other threads:[~2021-02-27 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-80774-4@http.gcc.gnu.org/bugzilla/>
2021-02-27 10:02 ` zeccav at gmail dot com [this message]
2021-05-14 9:48 ` [Bug fortran/80774] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:08 ` rguenth at gcc dot gnu.org
2022-05-27 9:37 ` [Bug fortran/80774] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:33 ` jakub at gcc dot gnu.org
2023-07-07 10:32 ` [Bug fortran/80774] [11/12/13/14 " rguenth 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-80774-4-DoViyTlVJc@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).