public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59780] New: ICE in aarch64_split_128bit_move Date: Sun, 12 Jan 2014 19:55:00 -0000 [thread overview] Message-ID: <bug-59780-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59780 Bug ID: 59780 Summary: ICE in aarch64_split_128bit_move Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org when building r206565 with target aarch64-linux-gnu I run into several ICEs like this: ... /home/vries/gcc_versions/devel/src/libgcc/soft-fp/negtf2.c: In function ‘__negtf2’: /home/vries/gcc_versions/devel/src/libgcc/soft-fp/negtf2.c:46:1: internal compiler error: RTL check: expected code 'reg', have 'const_int' in rhs_regno, at rtl.h:1125 } ^ 0xbde5de rtl_check_failed_code1(rtx_def const*, rtx_code, char const*, int, char const*) /home/vries/gcc_versions/devel/src/gcc/rtl.c:773 0xfe4c1d rhs_regno /home/vries/gcc_versions/devel/src/gcc/rtl.h:1125 0xfe62a1 aarch64_split_128bit_move(rtx_def*, rtx_def*) /home/vries/gcc_versions/devel/src/gcc/config/aarch64/aarch64.c:688 0x1048a60 gen_split_2245(rtx_def*, rtx_def**) /home/vries/gcc_versions/devel/src/gcc/config/aarch64/aarch64.md:752 b0x13fc389 split_1 /home/vries/gcc_versions/devel/src/gcc/config/aarch64/aarch64.md:751 0x1475285 split_insns(rtx_def*, rtx_def*) /home/vries/gcc_versions/devel/src/gcc/config/aarch64/aarch64.md:352 0x7ec8f6 try_split(rtx_def*, rtx_def*, int) /home/vries/gcc_versions/devel/src/gcc/emit-rtl.c:3471 0xb535ea split_insn /home/vries/gcc_versions/devel/src/gcc/recog.c:2850 0xb545f2 split_all_insns() /home/vries/gcc_versions/devel/src/gcc/recog.c:2940 0xb573f6 rest_of_handle_split_after_reload /home/vries/gcc_versions/devel/src/gcc/recog.c:3889 0xb57440 execute /home/vries/gcc_versions/devel/src/gcc/recog.c:3918 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. ... Investigating one of them shows: ... (gdb) down #6 0x0000000000fe62a2 in aarch64_split_128bit_move (dst=0x7ffff66fa0e0, src=0x7ffff687c470) at /home/vries/gcc_versions/devel/src/gcc/config/aarch64/aarch64.c:688 688 int src_regno = REGNO (src); (gdb) call debug_rtx (src) (const_int 0 [0]) (gdb) call debug_rtx (dst) (reg/v:TI 2 x2 [orig:80 _flo ] [80]) ... ... void aarch64_split_128bit_move (rtx dst, rtx src) { rtx low_dst; enum machine_mode src_mode = GET_MODE (src); enum machine_mode dst_mode = GET_MODE (dst); int src_regno = REGNO (src); int dst_regno = REGNO (dst); ... We're doing REGNO (src) while src == (const_int 0). >From gcc-bugs-return-440151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 12 20:14:48 2014 Return-Path: <gcc-bugs-return-440151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 6004 invoked by alias); 12 Jan 2014 20:14:47 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 5986 invoked by uid 48); 12 Jan 2014 20:14:43 -0000 From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59780] ICE in aarch64_split_128bit_move Date: Sun, 12 Jan 2014 20:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59780-4-Qesm4Kftfd@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59780-4@http.gcc.gnu.org/bugzilla/> References: <bug-59780-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-01/txt/msg01293.txt.bz2 Content-length: 1231 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY780 --- Comment #1 from vries at gcc dot gnu.org --- I'm using this as workaround for the moment: ... diff --git a/gcc/config/aarch64/aarch64.c b/gcc/config/aarch64/aarch64.c index 3b1f6b5..2c75c1c 100644 --- a/gcc/config/aarch64/aarch64.c +++ b/gcc/config/aarch64/aarch64.c @@ -685,7 +685,7 @@ aarch64_split_128bit_move (rtx dst, rtx src) enum machine_mode src_mode = GET_MODE (src); enum machine_mode dst_mode = GET_MODE (dst); - int src_regno = REGNO (src); + int src_regno; int dst_regno = REGNO (dst); gcc_assert (dst_mode == TImode || dst_mode == TFmode); @@ -693,6 +693,7 @@ aarch64_split_128bit_move (rtx dst, rtx src) if (REG_P (dst) && REG_P (src)) { gcc_assert (src_mode == TImode || src_mode == TFmode); + src_regno = REGNO (src); /* Handle r -> w, w -> r. */ if (FP_REGNUM_P (dst_regno) && GP_REGNUM_P (src_regno)) @@ -754,6 +755,7 @@ aarch64_split_128bit_move (rtx dst, rtx src) } return; case TFmode: + src_regno = REGNO (src); emit_move_insn (gen_rtx_REG (DFmode, dst_regno), gen_rtx_REG (DFmode, src_regno)); emit_move_insn (gen_rtx_REG (DFmode, dst_regno + 1), ...
next reply other threads:[~2014-01-12 19:55 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-12 19:55 vries at gcc dot gnu.org [this message] 2014-01-16 17:36 ` [Bug target/59780] " rearnsha at gcc dot gnu.org 2014-01-16 17:49 ` rearnsha 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-59780-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: 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).