public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org> To: gcc-gnats@gcc.gnu.org Subject: target/6927: ICE in final_scan_insn Date: Tue, 04 Jun 2002 05:16:00 -0000 [thread overview] Message-ID: <15612.44366.142965.401969@honolulu.ilog.fr> (raw) >Number: 6927 >Category: target >Synopsis: "could not split insn" error in C compiler for cris >Confidential: no >Severity: serious >Priority: low >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Tue Jun 04 05:16:02 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Bruno Haible >Release: 3.1 >Organization: GNU hackers >Environment: System: Linux linuix 2.4.18-4GB #1 Wed Mar 27 13:57:05 UTC 2002 i686 unknown Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: cris-axis-linux-gnu configured with: /packages2/gcc-3.1/configure --enable-shared --disable-nls --target=cris-linux --prefix=/cross/cris-linux-tools --with-local-prefix=/cross/cris-linux/local --with-as=/cross/cris-linux-tools/bin/cris-linux-as --with-gnu-as --with-ld=/cross/cris-linux-tools/bin/cris-linux-ld --with-gnu-ld --enable-languages=c >Description: Internal compiler error is signaled for this input file. It occurs when building glibc-2.2.5. ================================= swab.c =============================== void swab (const char *from, char *to, int n) { n &= ~1; while (n > 1) { const char b0 = from[--n], b1 = from[--n]; to[n] = b0; to[n + 1] = b1; } } ======================================================================== $ cris-linux-gcc -O2 -c /tmp/swab.c -o /tmp/swab.o /tmp/swab.c: In function `swab': /tmp/swab.c:10: could not split insn (insn 36 35 39 (parallel[ (set (mem:QI (plus:SI (reg/v/f:SI 11 r11 [24]) (reg/v:SI 12 r12 [25])) [0 S1 A8]) (reg/v:QI 9 r9 [26])) (set (reg/f:SI 9 r9 [30]) (plus:SI (reg/v/f:SI 11 r11 [24]) (reg/v:SI 12 r12 [25]))) ] ) 23 {*mov_sideqi_mem} (insn_list 30 (nil)) (nil)) /tmp/swab.c:10: Internal compiler error in final_scan_insn, at final.c:2622 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. >How-To-Repeat: See above. >Fix: Unknown. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-06-04 12:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=15612.44366.142965.401969@honolulu.ilog.fr \ --to=bruno@clisp.org \ --cc=gcc-gnats@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).