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: Tue, 16 Nov 2021 15:42:15 +0000 [thread overview]
Message-ID: <bug-103115-4-l2AfEV8u75@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
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
I can confirm the ICE with current trunk both on x86_64 and
on POWER.
x86_64:
$ gfortran -v
Es werden eingebaute Spezifikationen verwendet.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/home/ig25/libexec/gcc/x86_64-pc-linux-gnu/12.0.0/lto-wrapper
Ziel: x86_64-pc-linux-gnu
Konfiguriert mit: ../trunk/configure --prefix=/home/ig25
--enable-languages=c,c++,fortran --enable-maintainer-mode
Thread-Modell: posix
Unterstützte LTO-Kompressionsalgorithmen: zlib
gcc-Version 12.0.0 20211116 (experimental) [master revision
e87559d202d:f4e6da6e8ac:36ec54aac7da134441c83248e14825381b8d6f17] (GCC)
$ gfortran a.f90
a.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
0x808a8a tree_check_failed(tree_node const*, char const*, int, char const*,
...)
../../trunk/gcc/tree.c:8701
POWER:
tkoenig@gcc135 ~]$ gfortran -v
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/home/tkoenig/libexec/gcc/powerpc64le-unknown-linux-gnu/12.0.0/lto-wrapper
Target: powerpc64le-unknown-linux-gnu
Configured with: ../trunk/configure --prefix=/home/tkoenig
--enable-languages=c,c++,fortran
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 12.0.0 20211116 (experimental) (GCC)
[tkoenig@gcc135 ~]$ gfortran a.f90
a.f90:10:13:
10 | ]
| 1
internal compiler error: tree check: expected integer_cst, have save_expr in
gfc_trans_array_constructor_value, at fortran/trans-array.c:2187
0x1025d7ff tree_check_failed(tree_node const*, char const*, int, char const*,
...)
../../trunk/gcc/tree.c:8701
0x10408c23 tree_int_cst_elt_check(tree_node*, int, char const*, int, char
const*)
../../trunk/gcc/tree.h:3641
next prev parent reply other threads:[~2021-11-16 15:42 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 ` [Bug fortran/103115] [12 Regression] " tkoenig at gcc dot gnu.org
2021-11-16 12:29 ` 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 [this message]
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-l2AfEV8u75@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).