public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63805] ICE: in extract_insn, at recog.c:2327 with -mcpu=power8
Date: Wed, 25 Feb 2015 08:59:00 -0000 [thread overview]
Message-ID: <bug-63805-4-EhpzQ72e0y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63805-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63805
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
A smaller test case still fails with GCC 5.0.0 20150221, on both ppc64 and
ppc64le. 4.9.4 and 4.8.3 fail similarly.
$ cat u.cpp && /build/gcc-trunk/gcc/xgcc -B /build/gcc-trunk/gcc -O2 -S
-mcpu=power8 -xc++ u.cpp
struct A { long a; int b; };
struct B
{
struct { } c;
long a;
int b;
};
void foo (B);
void bar ()
{
A a;
__atomic_load (&a, &a, 0);
foo (B ());
}
u.cpp: In function ‘void bar()’:
u.cpp:17:1: error: unrecognizable insn:
}
^
(insn 5 2 6 2 (set (reg:PTI 156)
(unspec:PTI [
(mem/v:TI (plus:DI (reg/f:DI 150 virtual-stack-vars)
(const_int 24 [0x18])) [-1 S16 A128])
] UNSPEC_LSQ)) u.cpp:15 -1
(nil))
u.cpp:17:1: internal compiler error: in extract_insn, at recog.c:2343
0x109b11db _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/remote/msebor/fsf/gcc/trunk/gcc/rtl-error.c:110
0x109b1247 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
/home/remote/msebor/fsf/gcc/trunk/gcc/rtl-error.c:118
0x10977b87 extract_insn(rtx_insn*)
/home/remote/msebor/fsf/gcc/trunk/gcc/recog.c:2343
0x106e0ddf instantiate_virtual_regs_in_insn
/home/remote/msebor/fsf/gcc/trunk/gcc/function.c:1598
0x106e0ddf instantiate_virtual_regs
/home/remote/msebor/fsf/gcc/trunk/gcc/function.c:1966
0x106e0ddf execute
/home/remote/msebor/fsf/gcc/trunk/gcc/function.c:2015
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.
>From gcc-bugs-return-478407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 25 05:45:02 2015
Return-Path: <gcc-bugs-return-478407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96802 invoked by alias); 25 Feb 2015 05:45:02 -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 96708 invoked by uid 48); 25 Feb 2015 05:44:59 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64172] [4.9 Regression] Wrong code with GCC vector extensions on ARM when compiled without NEON
Date: Wed, 25 Feb 2015 09:03: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.2
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc
Message-ID: <bug-64172-4-pmE9Ruz1ya@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64172-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64172-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-02/txt/msg02739.txt.bz2
Content-length: 692
https://gcc.gnu.org/bugzilla/show_bug.cgi?idd172
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
Summary|[4.9/5 Regression] Wrong |[4.9 Regression] Wrong code
|code with GCC vector |with GCC vector extensions
|extensions on ARM when |on ARM when compiled
|compiled without NEON |without NEON
--- Comment #15 from Jeffrey A. Law <law at redhat dot com> ---
Fixed by Vlad's commit on the trunk.
prev parent reply other threads:[~2015-02-25 4:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 12:01 [Bug target/63805] New: [4.9/4.8/5 Regression] ICE: in extract_insn, at recog.c:2154 " trippels at gcc dot gnu.org
2014-11-10 13:40 ` [Bug target/63805] ICE: in extract_insn, at recog.c:2327 " trippels at gcc dot gnu.org
2014-11-10 14:10 ` rguenth at gcc dot gnu.org
2014-12-21 8:26 ` dimhen at gmail dot com
2015-02-25 8:59 ` msebor at gcc dot gnu.org [this message]
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-63805-4-EhpzQ72e0y@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).