public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mscfd at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/105054] Using one kind of pointer functions causes the compiler to hang
Date: Fri, 25 Mar 2022 13:45:21 +0000 [thread overview]
Message-ID: <bug-105054-4-7h6vWRVbBr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105054-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105054
martin <mscfd at gmx dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mscfd at gmx dot net
--- Comment #1 from martin <mscfd at gmx dot net> ---
Confirmed with the current development branch for gfortran-12.
Moreover, if I comment out the program beginning from line
pointer_to_string(2) = '12345678901234567890'
to the end, (hence "pointer_to_string(1) = '1234567890'" is the last
uncommented line), then I get an ICE:
during RTL pass: expand
pointer_to_string.f90:20:26:
20 | program chk_string_pointer
| ^
internal compiler error: in expand_expr_real_1, at expr.cc:10585
0x68336a expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
../../gcc/expr.cc:10585
0x908991 expand_normal
../../gcc/expr.h:307
0x908991 do_compare_and_jump
../../gcc/dojump.cc:1253
0x90999a do_jump_1
../../gcc/dojump.cc:253
0x89f6c1 expand_gimple_cond
../../gcc/cfgexpand.cc:2645
0x89f6c1 expand_gimple_basic_block
../../gcc/cfgexpand.cc:5933
0x8a0536 execute
../../gcc/cfgexpand.cc:6806
next prev parent reply other threads:[~2022-03-25 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 13:02 [Bug fortran/105054] New: " arjen.markus895 at gmail dot com
2022-03-25 13:45 ` mscfd at gmx dot net [this message]
2022-03-25 14:26 ` [Bug fortran/105054] [11/12 Regression] Using one kind of pointer functions causes the compiler to hang since r11-3029-g2b0df0a6ac79b34f marxin at gcc dot gnu.org
2022-04-04 11:32 ` rguenth at gcc dot gnu.org
2022-04-21 7:51 ` rguenth at gcc dot gnu.org
2023-05-29 10:06 ` [Bug fortran/105054] [11/12/13/14 " jakub 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-105054-4-7h6vWRVbBr@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).