public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/103115] [12 Regression] reallocation of character array fails when appending a constant size 4 array
Date: Mon, 15 Nov 2021 19:32:31 +0000 [thread overview]
Message-ID: <bug-103115-4-rehBkn0bEg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103115-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103115
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code,
| |wrong-code
Status|UNCONFIRMED |NEW
Summary|reallocation of character |[12 Regression]
|array fails when appending |reallocation of character
|a constant size 4 array |array fails when appending
| |a constant size 4 array
Ever confirmed|0 |1
Target Milestone|--- |12.0
Last reconfirmed| |2021-11-15
CC| |tkoenig at gcc dot gnu.org
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
I can confirm the bug with gcc 9 (didn't check any other
version).
Current trunk gives me
.f90:10:13:
10 | ]
| 1
interner Compiler-Fehler: tree check: expected integer_cst, have save_expr in
gfc_trans_array_constructor_value, at fortran/trans-array.c:2187
0x1002ebcf tree_check_failed(tree_node const*, char const*, int, char const*,
...)
../../trunk/gcc/tree.c:8689
0x101d89bf tree_int_cst_elt_check(tree_node*, int, char const*, int, char
const*)
../../trunk/gcc/tree.h:3633
0x101d89bf tree_int_cst_elt_check(tree_node*, int, char const*, int, char
const*)
../../trunk/gcc/tree.h:3629
0x101d89bf gfc_trans_array_constructor_value
../../trunk/gcc/fortran/trans-array.c:2187
0x101d9563 trans_array_constructor
../../trunk/gcc/fortran/trans-array.c:2900
0x101d9563 gfc_add_loop_ss_code
../../trunk/gcc/fortran/trans-array.c:3180
0x101d9f6f gfc_conv_loop_setup(gfc_loopinfo*, locus*)
../../trunk/gcc/fortran/trans-array.c:5430
0x102350db gfc_trans_assignment_1
../../trunk/gcc/fortran/trans-expr.c:11642
0x101ba337 trans_code
../../trunk/gcc/fortran/trans.c:1916
Marking as regression for the ICE at least.
next prev parent reply other threads:[~2021-11-15 19:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 11:01 [Bug fortran/103115] New: " ygalklein at gmail dot com
2021-11-07 11:05 ` [Bug fortran/103115] " ygalklein at gmail dot com
2021-11-15 19:32 ` tkoenig at gcc dot gnu.org [this message]
2021-11-16 12:29 ` [Bug fortran/103115] [12 Regression] " juergen.reuter at desy dot de
2021-11-16 13:07 ` tkoenig at gcc dot gnu.org
2021-11-16 15:42 ` tkoenig at gcc dot gnu.org
2021-11-17 9:07 ` juergen.reuter at desy dot de
2021-11-17 16:30 ` tkoenig at gcc dot gnu.org
2022-01-17 13:00 ` rguenth at gcc dot gnu.org
2022-05-06 8:31 ` [Bug fortran/103115] [12/13 " jakub at gcc dot gnu.org
2023-05-08 12:23 ` [Bug fortran/103115] [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-103115-4-rehBkn0bEg@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).