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/100154] New: [9/10/11 Regression] ICE in gfc_conv_procedure_call, at fortran/trans-expr.c:6131
Date: Tue, 20 Apr 2021 17:36:04 +0000 [thread overview]
Message-ID: <bug-100154-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100154
Bug ID: 100154
Summary: [9/10/11 Regression] ICE in gfc_conv_procedure_call,
at fortran/trans-expr.c:6131
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Changed between 20180916 and 20180923 :
$ cat z1.f90
program p
n = fget('c')
end
$ gfortran-9-20180916 -c z1.f90
$
$ gfortran-11-20210418 -c z1.f90
z1.f90:2:16:
2 | n = fget('c')
| 1
internal compiler error: Segmentation fault
0xc0b22f crash_signal
../../gcc/toplev.c:327
0x771d0f gfc_conv_procedure_call(gfc_se*, gfc_symbol*, gfc_actual_arglist*,
gfc_expr*, vec<tree_node*, va_gc, vl_embed>*)
../../gcc/fortran/trans-expr.c:6131
0x78e23e gfc_conv_intrinsic_funcall
../../gcc/fortran/trans-intrinsic.c:4443
0x791467 gfc_conv_intrinsic_function(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-intrinsic.c:10170
0x76766a gfc_conv_expr(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-expr.c:8967
0x7774a1 gfc_trans_assignment_1
../../gcc/fortran/trans-expr.c:11259
0x739707 trans_code
../../gcc/fortran/trans.c:1932
0x75fd34 gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6884
0x6e66b6 translate_all_program_units
../../gcc/fortran/parse.c:6351
0x6e66b6 gfc_parse_file()
../../gcc/fortran/parse.c:6620
0x7329cf gfc_be_parse_file
../../gcc/fortran/f95-lang.c:212
next reply other threads:[~2021-04-20 17:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 17:36 gscfq@t-online.de [this message]
2021-04-20 20:58 ` [Bug fortran/100154] " anlauf at gcc dot gnu.org
2021-04-20 21:21 ` anlauf at gcc dot gnu.org
2021-04-21 6:19 ` marxin at gcc dot gnu.org
2021-04-21 8:51 ` burnus at gcc dot gnu.org
2021-04-21 20:00 ` [Bug fortran/100154] [9/10/11/12 " anlauf at gcc dot gnu.org
2021-04-21 20:09 ` anlauf at gcc dot gnu.org
2021-04-21 20:36 ` anlauf at gcc dot gnu.org
2021-04-21 20:55 ` anlauf at gcc dot gnu.org
2021-04-22 21:06 ` anlauf at gcc dot gnu.org
2021-04-24 18:52 ` cvs-commit at gcc dot gnu.org
2021-04-24 19:48 ` anlauf at gcc dot gnu.org
2021-04-27 21:13 ` cvs-commit at gcc dot gnu.org
2021-04-27 21:29 ` cvs-commit at gcc dot gnu.org
2021-04-27 21:41 ` cvs-commit at gcc dot gnu.org
2021-04-27 21:42 ` 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-100154-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).