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/104131] ICE in gfc_conv_array_ref, at fortran/trans-array.c:3810
Date: Wed, 26 Jan 2022 17:25:05 +0000 [thread overview]
Message-ID: <bug-104131-4-9Bwur9BqWM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104131-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104131
--- Comment #2 from G. Steinmetz <gscfq@t-online.de> ---
And with a coarray :
$ cat zz1.f90
program p
use iso_c_binding, only: c_intptr_t
integer, parameter :: omp_event_handle_kind = c_intptr_t
integer (kind=omp_event_handle_kind) :: x[*]
!$omp task detach (x)
!$omp end task
end
$ cat zz2.f90
program p
use iso_c_binding, only: c_intptr_t
integer, parameter :: omp_event_handle_kind = c_intptr_t
integer (kind=omp_event_handle_kind) :: x[*]
!$omp parallel master default (none)
!$omp task detach (x)
!$omp end task
!$omp end parallel master
end
$ gfortran-12-20220123 -c zz1.f90 -fopenmp -fcoarray=single
zz1.f90:5:24:
5 | !$omp task detach (x)
| ^
internal compiler error: Segmentation fault
0xcc430f crash_signal
../../gcc/toplev.cc:322
0xa229da omp_add_variable
../../gcc/gimplify.cc:7200
0xa32f20 gimplify_scan_omp_clauses
../../gcc/gimplify.cc:10305
0xa267ce gimplify_omp_task
../../gcc/gimplify.cc:12122
0xa267ce gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
../../gcc/gimplify.cc:15454
0xa29b18 gimplify_stmt(tree_node**, gimple**)
../../gcc/gimplify.cc:7035
0xa2a071 gimplify_bind_expr
../../gcc/gimplify.cc:1427
0xa2745a gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
../../gcc/gimplify.cc:15161
0xa29b18 gimplify_stmt(tree_node**, gimple**)
../../gcc/gimplify.cc:7035
0xa2ab9b gimplify_body(tree_node*, bool)
../../gcc/gimplify.cc:16206
0xa2afef gimplify_function_tree(tree_node*)
../../gcc/gimplify.cc:16360
0x8b26f7 cgraph_node::analyze()
../../gcc/cgraphunit.cc:675
0x8b50a7 analyze_functions
../../gcc/cgraphunit.cc:1240
0x8b5a6d symbol_table::finalize_compilation_unit()
../../gcc/cgraphunit.cc:2500
next prev parent reply other threads:[~2022-01-26 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 18:53 [Bug fortran/104131] New: " gscfq@t-online.de
2022-01-20 10:19 ` [Bug fortran/104131] " marxin at gcc dot gnu.org
2022-01-26 17:25 ` gscfq@t-online.de [this message]
2022-03-03 10:28 ` cvs-commit at gcc dot gnu.org
2023-10-23 18:50 ` anlauf at gcc dot gnu.org
2023-10-23 19:15 ` anlauf at gcc dot gnu.org
2023-10-24 19:53 ` burnus at gcc dot gnu.org
2023-10-24 20:26 ` anlauf at gcc dot gnu.org
2023-10-25 7:07 ` burnus 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-104131-4-9Bwur9BqWM@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).