public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50410] [8/9/10/11 Regression] ICE in record_reference, pointer variable in data statement
Date: Mon, 11 May 2020 06:09:56 +0000 [thread overview]
Message-ID: <bug-50410-4-dqNxtbRihj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50410-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50410
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |kargl at gcc dot gnu.org
Resolution|FIXED |---
Target Milestone|8.5 |11.0
--- Comment #39 from kargl at gcc dot gnu.org ---
The bug is not fixed. The code from comment #3
% cat a.f90
type t
integer g
end type
type(t) :: u=t(1)
data u%g /2/
end
troutmask:sgk[205] gfcx -c a.f90
a.f90:1:0:
1 | type t
|
internal compiler error: Segmentation fault
0xdf6e3a crash_signal
../../gccx/gcc/toplev.c:328
0x8acbae gfc_conv_structure(gfc_se*, gfc_expr*, int)
../../gccx/gcc/fortran/trans-expr.c:8528
0x8c1f37 gfc_conv_initializer(gfc_expr*, gfc_typespec*, tree_node*, bool, bool,
bool)
../../gccx/gcc/fortran/trans-expr.c:7679
0x8a0020 gfc_get_symbol_decl(gfc_symbol*)
../../gccx/gcc/fortran/trans-decl.c:1892
0x8a33e5 generate_local_decl
../../gccx/gcc/fortran/trans-decl.c:5894
0x85a0e2 do_traverse_symtree
../../gccx/gcc/fortran/symbol.c:4165
0x8a454c generate_local_vars
../../gccx/gcc/fortran/trans-decl.c:6100
0x8a454c gfc_generate_function_code(gfc_namespace*)
../../gccx/gcc/fortran/trans-decl.c:6758
0x81e516 translate_all_program_units
../../gccx/gcc/fortran/parse.c:6302
0x81e516 gfc_parse_file()
../../gccx/gcc/fortran/parse.c:6541
0x871858 gfc_be_parse_file
../../gccx/gcc/fortran/f95-lang.c:210
The code in the first example in comment #9 also causes an ICE.
Codes z1.f90, z2.f90, and z3.f90 in comment #23 cause ICEs.
next prev parent reply other threads:[~2020-05-11 6:09 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 8:43 [Bug fortran/50410] New: ICE in record_reference zeccav at gmail dot com
2011-09-15 11:16 ` [Bug fortran/50410] [4.6/4.7 Regression] " dominiq at lps dot ens.fr
2011-09-18 22:01 ` zeccav at gmail dot com
2011-09-18 22:02 ` dominiq at lps dot ens.fr
2011-09-19 0:46 ` kargl at gcc dot gnu.org
2011-09-21 19:17 ` janus at gcc dot gnu.org
2011-09-29 13:23 ` rguenth at gcc dot gnu.org
2011-10-10 13:59 ` rguenth at gcc dot gnu.org
2011-10-17 16:39 ` burnus at gcc dot gnu.org
2011-10-17 17:37 ` kargl at gcc dot gnu.org
2011-10-17 21:21 ` burnus at gcc dot gnu.org
2011-10-18 7:23 ` burnus at gcc dot gnu.org
2011-10-26 17:37 ` jakub at gcc dot gnu.org
2012-01-02 12:32 ` burnus at gcc dot gnu.org
2012-03-01 15:01 ` jakub at gcc dot gnu.org
2013-04-12 15:17 ` [Bug fortran/50410] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2014-06-12 13:48 ` [Bug fortran/50410] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:34 ` [Bug fortran/50410] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-23 8:28 ` [Bug fortran/50410] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 20:02 ` [Bug fortran/50410] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:30 ` jakub at gcc dot gnu.org
2015-09-02 13:14 ` zeccav at gmail dot com
2020-05-11 4:57 ` [Bug fortran/50410] [8/9/10/11 Regression] ICE in record_reference, pointer variable in data statement zeccav at gmail dot com
2020-05-11 4:58 ` zeccav at gmail dot com
2020-05-11 6:09 ` kargl at gcc dot gnu.org [this message]
2020-06-20 19:29 ` anlauf at gcc dot gnu.org
2020-06-21 15:31 ` dominiq at lps dot ens.fr
2020-06-21 17:20 ` anlauf at gcc dot gnu.org
2020-06-21 18:19 ` anlauf at gcc dot gnu.org
2021-04-27 11:37 ` [Bug fortran/50410] [8/9/10/11/12 " jakub at gcc dot gnu.org
2021-07-28 7:04 ` [Bug fortran/50410] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-04-21 7:47 ` rguenth at gcc dot gnu.org
2023-05-29 10:01 ` [Bug fortran/50410] [10/11/12/13/14 " jakub at gcc dot gnu.org
2023-07-31 20:49 ` [Bug fortran/50410] [11/12/13/14 " anlauf at gcc dot gnu.org
2024-03-29 9:32 ` cvs-commit at gcc dot gnu.org
2024-03-29 17:02 ` cvs-commit at gcc dot gnu.org
2024-03-29 17:25 ` cvs-commit at gcc dot gnu.org
2024-03-29 17:43 ` cvs-commit at gcc dot gnu.org
2024-03-29 17:50 ` [Bug fortran/50410] " 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-50410-4-dqNxtbRihj@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).