public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sumbera at volny dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/105792] New: SPARC GCC 12.1.0 fails with internal compiler error: in expand_expr_real_2, at expr.cc:10160
Date: Tue, 31 May 2022 14:43:30 +0000 [thread overview]
Message-ID: <bug-105792-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105792
Bug ID: 105792
Summary: SPARC GCC 12.1.0 fails with internal compiler error:
in expand_expr_real_2, at expr.cc:10160
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: sumbera at volny dot cz
Target Milestone: ---
GDB and Qt5 fails with the same internal error when building with GCC 12.1.0 on
Solaris SPARC. GCC 11 works wiyhout problem. Following is GDB error output:
gmake[3]: Entering directory
'/scratch/psumbera/userland-test/components/gdb/build/sparcv9/readline/readline'
rm -f rltty.o
/usr/gcc/12/bin/gcc -std=gnu99 -c -DHAVE_CONFIG_H -I.
-I/scratch/psumbera/userland-test/components/gdb/gdb-10.2/readline/readline
-DRL_LIBRARY_VERSION='"8.0"' -m64 -Wall -Wno-long-long -Wcast-align
-fno-omit-frame-pointer -O2 -mcpu=ultrasparc3 -mtune=niagara4
-mno-unaligned-doubles -mapp-regs -mhard-float
/scratch/psumbera/userland-test/components/gdb/gdb-10.2/readline/readline/rltty.c
during RTL pass: expand
In function 'save_tty_chars',
inlined from 'rl_prep_terminal' at
/scratch/psumbera/userland-test/components/gdb/gdb-10.2/readline/readline/rltty.c:638:3:
/scratch/psumbera/userland-test/components/gdb/gdb-10.2/readline/readline/rltty.c:370:52:
internal compiler error: in expand_expr_real_2, at expr.cc:10160
370 | _rl_intr_char = _rl_tty_chars.t_intr = tiop->c_cc[VINTR];
| ~~~~~~~~~~^~~~~~~
0x1007f0ff3 expand_expr_real_2(separate_ops*, rtx_def*, machine_mode,
expand_modifier)
/builds/psumbera/userland-gcc-12.1.0/components/gcc12/gcc-12.1.0/gcc/expr.cc:10160
0x10069f793 expand_gimple_stmt_1
/builds/psumbera/userland-gcc-12.1.0/components/gcc12/gcc-12.1.0/gcc/cfgexpand.cc:3972
0x10069f793 expand_gimple_stmt
/builds/psumbera/userland-gcc-12.1.0/components/gcc12/gcc-12.1.0/gcc/cfgexpand.cc:4033
0x1006a5313 expand_gimple_basic_block
/builds/psumbera/userland-gcc-12.1.0/components/gcc12/gcc-12.1.0/gcc/cfgexpand.cc:6080
0x1006a71a7 execute
/builds/psumbera/userland-gcc-12.1.0/components/gcc12/gcc-12.1.0/gcc/cfgexpand.cc:6806
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
gmake[3]: *** [Makefile:105: rltty.o] Error 1
gmake[3]: Leaving directory
'/scratch/psumbera/userland-test/components/gdb/build/sparcv9/readline/readline'
--
Lowering optimization level to -O1 or -O0 helps (-O3 doesn't help).
Also when '-mcpu=ultrasparc3' isn't included it helps.
next reply other threads:[~2022-05-31 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 14:43 sumbera at volny dot cz [this message]
2022-05-31 14:45 ` [Bug target/105792] " pinskia at gcc dot gnu.org
2022-05-31 14:52 ` sumbera at volny dot cz
2022-06-01 3:31 ` sam at gentoo dot org
2022-06-02 14:11 ` sumbera at volny dot cz
2022-06-03 11:02 ` ebotcazou 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-105792-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).