public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "christian.ehrhardt at canonical dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/106966] alpha cross build crashes gcc-12 "internal compiler error: in emit_move_insn" Date: Mon, 19 Sep 2022 11:11:57 +0000 [thread overview] Message-ID: <bug-106966-4-ZOgr8yNnYp@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 --- Comment #1 from Christian Ehrhardt <christian.ehrhardt at canonical dot com> --- I compared a few more cross-gcc's I could get hold of. Thereby I can state this was already broken with 12.1.0 on Ubuntu 22.04 and Fedora 36. Note: I'm only listing where the instructions for these differ 1. Fedora 36 gcc version 12.1.1 20220507 (Red Hat Cross 12.1.1-1) (GCC) $ dnf install gcc-alpha-linux-gnu make git ... alpha-linux-gnu-gcc -O2 -g1 -Wall -fvisibility=hidden -fno-strict-aliasing -msmall-text -msmall-data -mno-fp-regs -mbuild-constants -mcpu=ev67 -DSYSTEM_H='"sys-clipper.h"' -c -o console.o console.c during RTL pass: expand console.c: In function ‘do_console’: console.c:130:12: internal compiler error: in emit_move_insn, at expr.cc:4010 130 | vga[0] = 'H' + attr; | ~~~~~~~^~~~~~~~~~~~ Please submit a full bug report, with preprocessed source (by using -freport-bug). See <http://bugzilla.redhat.com/bugzilla/> for instructions. Preprocessed source stored into /tmp/cchVNtxj.out file, please attach this to your bugreport. make: *** [<builtin>: console.o] Error 1 2. Ubuntu 22.04 gcc-12 gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) $ apt install gcc-12-alpha-linux-gnu ... alpha-linux-gnu-gcc-12 -O2 -g1 -Wall -fvisibility=hidden -fno-strict-aliasing -msmall-text -msmall-data -mno-fp-regs -mbuild-constants -mcpu=ev67 -DSYSTEM_H='"sys-clipper.h"' -c -o console.o console.c during RTL pass: expand console.c: In function ‘do_console’: console.c:130:12: internal compiler error: in emit_move_insn, at expr.cc:4010 130 | vga[0] = 'H' + attr; | ~~~~~~~^~~~~~~~~~~~ 0x13767bb internal_error(char const*, ...) ???:0 0x5a92b0 fancy_abort(char const*, int, char const*) ???:0 0xe09a32 alpha_split_const_mov(machine_mode, rtx_def**) ???:0 0xe09ba1 alpha_expand_mov(machine_mode, rtx_def**) ???:0 0x112c7fd gen_movv4hi(rtx_def*, rtx_def*) ???:0 0x7ee88b emit_move_insn_1(rtx_def*, rtx_def*) ???:0 0x7eec77 emit_move_insn(rtx_def*, rtx_def*) ???:0 0xe0c3b6 alpha_expand_movmisalign(machine_mode, rtx_def**) ???:0 0x112caca gen_movmisalignv4hi(rtx_def*, rtx_def*) ???:0 0xa272fc expand_insn(insn_code, unsigned int, expand_operand*) ???:0 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <file:///usr/share/doc/gcc-12/README.Bugs> for instructions. make: *** [<builtin>: console.o] Error 1
next prev parent reply other threads:[~2022-09-19 11:11 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 ` christian.ehrhardt at canonical dot com [this message] 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 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-ZOgr8yNnYp@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: linkBe 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).