public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106966] alpha cross build crashes gcc-12 "internal compiler error: in emit_move_insn"
Date: Fri, 23 Sep 2022 08:20:40 +0000 [thread overview]
Message-ID: <bug-106966-4-9YI8yHNR6L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106966-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106966
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2022-09-23
--- Comment #6 from Uroš Bizjak <ubizjak at gmail dot com> ---
Testcase:
void
do_console (unsigned short *vga)
{
vga[0] = 'H';
vga[1] = 'e';
vga[2] = 'l';
vga[3] = 'l';
vga[4] = 'o';
}
cc1 -O2 -mbuild-constants:
during RTL pass: expand
pr106966.c: In function ‘do_console’:
pr106966.c:4:10: internal compiler error: in emit_move_insn, at expr.cc:4052
4 | vga[0] = 'H';
| ~~~~~~~^~~~~
0x5ed664 emit_move_insn(rtx_def*, rtx_def*)
../../git/gcc/gcc/expr.cc:4052
0x113a708 alpha_emit_set_long_const
../../git/gcc/gcc/config/alpha/alpha.cc:2090
0x113abfc alpha_split_const_mov(machine_mode, rtx_def**)
../../git/gcc/gcc/config/alpha/alpha.cc:2204
0x113ade7 alpha_expand_mov(machine_mode, rtx_def**)
../../git/gcc/gcc/config/alpha/alpha.cc:2250
0x15510a8 gen_movv4hi(rtx_def*, rtx_def*)
../../git/gcc/gcc/config/alpha/alpha.md:4463
...
(gdb) bt
#0 internal_error (gmsgid=gmsgid@entry=0x1a9cf85 "in %s, at %s:%d") at
../../git/gcc/gcc/diagnostic.cc:2107
#1 0x00000000007918d6 in fancy_abort (file=file@entry=0x1910cf9
"../../git/gcc/gcc/expr.cc", line=line@entry=4052,
function=function@entry=0x1a23a78 "emit_move_insn") at
../../git/gcc/gcc/diagnostic.cc:2211
#2 0x00000000005ed665 in emit_move_insn (x=<optimized out>, y=<optimized out>)
at ../../git/gcc/gcc/expr.cc:4052
#3 0x000000000113a709 in alpha_emit_set_long_const (target=0x7fffea2ef9f0,
c1=7077888) at ../../git/gcc/gcc/config/alpha/alpha.cc:2090
#4 0x000000000113abfd in alpha_split_const_mov (mode=E_V4HImode,
operands=0x7fffffffd5a0) at ../../git/gcc/gcc/config/alpha/alpha.cc:2204
#5 0x000000000113ade8 in alpha_expand_mov (mode=E_V4HImode,
operands=0x7fffffffd5a0) at ../../git/gcc/gcc/config/alpha/alpha.cc:2250
#6 0x00000000015510a9 in gen_movv4hi (operand0=0x7fffea2ef9f0,
operand1=0x7fffea29ebc0) at ../../git/gcc/gcc/config/alpha/alpha.md:4463
(gdb) f 3
#3 0x000000000113a709 in alpha_emit_set_long_const (target=0x7fffea2ef9f0,
c1=7077888) at ../../git/gcc/gcc/config/alpha/alpha.cc:2090
2090 emit_move_insn (target, gen_rtx_PLUS (DImode, target, GEN_INT
(d3)));
(gdb) p debug_rtx (target)
(reg:V4HI 71)
$1 = void
next prev parent reply other threads:[~2022-09-23 8:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 10:56 [Bug c/106966] New: " christian.ehrhardt at canonical dot com
2022-09-19 11:11 ` [Bug c/106966] " christian.ehrhardt at canonical dot com
2022-09-19 13:49 ` [Bug target/106966] " ubizjak at gmail dot com
2022-09-19 14:15 ` christian.ehrhardt at canonical dot com
2022-09-20 7:19 ` ubizjak at gmail dot com
2022-09-22 6:30 ` christian.ehrhardt at canonical dot com
2022-09-23 8:20 ` ubizjak at gmail dot com [this message]
2023-07-08 12:11 ` ubizjak at gmail dot com
2023-07-08 13:47 ` ubizjak at gmail dot com
2023-07-08 13:50 ` [Bug target/106966] [12/13/14 Regression] " ubizjak at gmail dot com
2023-07-10 3:58 ` matoro_gcc_bugzilla at matoro dot tk
2023-07-10 6:32 ` ubizjak at gmail dot com
2023-07-10 14:41 ` matoro_gcc_bugzilla at matoro dot tk
2023-07-10 15:05 ` doko at gcc dot gnu.org
2023-07-13 13:19 ` doko at gcc dot gnu.org
2023-07-13 16:32 ` cvs-commit at gcc dot gnu.org
2023-07-13 16:34 ` cvs-commit at gcc dot gnu.org
2023-07-13 16:34 ` cvs-commit at gcc dot gnu.org
2023-07-13 16:37 ` ubizjak at gmail dot com
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-106966-4-9YI8yHNR6L@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).