public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63666] New: [5.0 regression] FAIL: gcc.dg/vect/pr45752.c (internal compiler error)
Date: Tue, 28 Oct 2014 10:27:00 -0000 [thread overview]
Message-ID: <bug-63666-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63666
Bug ID: 63666
Summary: [5.0 regression] FAIL: gcc.dg/vect/pr45752.c (internal
compiler error)
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: schwab@linux-m68k.org
CC: rguenther at suse dot de
Target: ia64-*-*
Broken by r216728.
$ gcc/xgcc -Bgcc/ ../gcc/testsuite/gcc.dg/vect/pr45752.c -ftree-vectorize
-fno-vect-cost-model -fno-common -O2 -fdump-tree-vect-details -lm -o
./pr45752.exe
../gcc/testsuite/gcc.dg/vect/pr45752.c: In function ‘foo’:
../gcc/testsuite/gcc.dg/vect/pr45752.c:38:6: internal compiler error: in
ia64_vectorize_vec_perm_const_ok, at config/ia64/ia64.c:11728
void foo (unsigned int *__restrict__ pInput,
^
0x4000000001069d9f ia64_vectorize_vec_perm_const_ok
../../gcc/config/ia64/ia64.c:11728
0x400000000090272f can_vec_perm_p(machine_mode, bool, unsigned char const*)
../../gcc/optabs.c:6611
0x4000000000f387df vect_transform_slp_perm_load(_slp_tree*, vec<tree_node*,
va_heap, vl_ptr>, gimple_stmt_iterator*, int, _slp_instance*, bool)
../../gcc/tree-vect-slp.c:3049
0x4000000000f3c99f vect_supported_load_permutation_p
../../gcc/tree-vect-slp.c:1349
0x4000000000f3c99f vect_analyze_slp_instance
../../gcc/tree-vect-slp.c:1677
0x4000000000f3d28f vect_analyze_slp(_loop_vec_info*, _bb_vec_info*, unsigned
int)
../../gcc/tree-vect-slp.c:1747
0x4000000000f1674f vect_analyze_loop_2
../../gcc/tree-vect-loop.c:1762
0x4000000000f1674f vect_analyze_loop(loop*)
../../gcc/tree-vect-loop.c:1875
0x4000000000f4659f vectorize_loops()
../../gcc/tree-vectorizer.c:442
0x4000000000d77abf execute
../../gcc/tree-ssa-loop.c:290
>From gcc-bugs-return-465118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Oct 28 10:27:18 2014
Return-Path: <gcc-bugs-return-465118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26223 invoked by alias); 28 Oct 2014 10:27:18 -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 26195 invoked by uid 48); 28 Oct 2014 10:27:14 -0000
From: "jiwang at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63666] [5.0 regression] FAIL: gcc.dg/vect/pr45752.c (internal compiler error)
Date: Tue, 28 Oct 2014 10:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jiwang 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: cc
Message-ID: <bug-63666-4-cbaEbKGL0M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63666-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63666-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-10/txt/msg02139.txt.bz2
Content-length: 1170
https://gcc.gnu.org/bugzilla/show_bug.cgi?idc666
Jiong Wang <jiwang at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jiwang at gcc dot gnu.org
--- Comment #1 from Jiong Wang <jiwang at gcc dot gnu.org> ---
I noticed this on aarch64 platform also and I suspect it's caused by
commit f619ecaed41d1487091098a0f4fdf4d6ed1fa379
Author: rguenth <rguenth@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Mon Oct 27 11:30:23 2014 +0000
2014-10-27 Richard Biener <rguenther@suse.de>
* tree-ssa-forwprop.c: Include tree-cfgcleanup.h and tree-into-ssa.h.
(lattice): New global.
(fwprop_ssa_val): New function.
(fold_all_stmts): Likewise.
(pass_forwprop::execute): Finally fold all stmts.
* gcc.dg/tree-ssa/forwprop-6.c: Scan ccp1 dump instead.
* gcc.dg/strlenopt-8.c: Adjust and XFAIL for non_strict_align
target due to memcpy inline-expansion.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@216728
138bc75d-0d04-0410-961f-82ee72b054a4
next reply other threads:[~2014-10-28 10:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 10:27 schwab@linux-m68k.org [this message]
2014-10-28 11:01 ` [Bug tree-optimization/63666] " schwab@linux-m68k.org
2014-10-28 11:37 ` rguenth at gcc dot gnu.org
2014-10-28 11:41 ` jiwang at gcc dot gnu.org
2014-10-28 11:43 ` rguenth at gcc dot gnu.org
2014-10-29 9:23 ` rguenth at gcc dot gnu.org
2014-10-29 9:25 ` rguenth at gcc dot gnu.org
2014-10-29 12:36 ` jiwang at gcc dot gnu.org
2014-10-29 13:07 ` rguenther at suse dot de
2014-10-29 13:18 ` rguenth at gcc dot gnu.org
2014-10-29 22:07 ` glisse 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-63666-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: 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).