[Bug target/60950] powerpc-e500v2-linux-gnuspe: ICE in extract_insn, at recog.c:2202

["msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60950

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |msebor at gcc dot gnu.org

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
This ICE still appears to exist today (r221777):

$ ./gcc/xgcc -Bgcc -O3 -S -o/dev/tty t.c || ./gcc/xgcc -v
    .file    "t.c"
t.c: In function ‘e5’:
t.c:33:1: error: unrecognizable insn:
 }
 ^
(insn 236 235 126 10 (set (reg:CC 75 7 [275])
        (compare:CC (reg:HI 10 10)
            (const_int 0 [0]))) t.c:26 -1
     (nil))
t.c:33:1: internal compiler error: in extract_insn, at recog.c:2343
0xa17f08 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
    /home/msebor/fsf/gcc-git/gcc/rtl-error.c:110
0xa17f39 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
    /home/msebor/fsf/gcc-git/gcc/rtl-error.c:118
0x9ea867 extract_insn(rtx_insn*)
    /home/msebor/fsf/gcc-git/gcc/recog.c:2343
0x9ea8f1 extract_insn_cached(rtx_insn*)
    /home/msebor/fsf/gcc-git/gcc/recog.c:2234
0x78be0d cleanup_subreg_operands(rtx_insn*)
    /home/msebor/fsf/gcc-git/gcc/final.c:3137
0x9e811f split_insn
    /home/msebor/fsf/gcc-git/gcc/recog.c:2957
0x9ecc6f split_all_insns()
    /home/msebor/fsf/gcc-git/gcc/recog.c:3011
0x9ecd12 rest_of_handle_split_after_reload
    /home/msebor/fsf/gcc-git/gcc/recog.c:3958
0x9ecd12 execute
    /home/msebor/fsf/gcc-git/gcc/recog.c:3987
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.
Using built-in specs.
COLLECT_GCC=./gcc/xgcc
Target: powerpc-linux-gnuspe
Configured with: /home/msebor/fsf/gcc-git/configure --disable-bootstrap
--enable-languages=c --target=powerpc-linux-gnuspe
Thread model: posix
gcc version 5.0.0 20150330 (experimental) (GCC)
>From gcc-bugs-return-482438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Mar 31 17:58:01 2015
Return-Path: <gcc-bugs-return-482438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79301 invoked by alias); 31 Mar 2015 17:58:01 -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 79220 invoked by uid 48); 31 Mar 2015 17:57:57 -0000
From: "kariya_mitsuru at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65398] [5 Regression] [C++11] GCC rejects constexpr variable definitions with valid initialization
Date: Tue, 31 Mar 2015 18:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kariya_mitsuru at hotmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65398-4-hJslqXMHur@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65398-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: 2015-03/txt/msg03582.txt.bz2
Content-length: 234

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide398

--- Comment #15 from Mitsuru Kariya <kariya_mitsuru at hotmail dot com> ---
I have opened a new issue bug 65642.
(Sorry, I made a mistake in operation so its description is empty.)