From: James Greenhalgh <james.greenhalgh@arm.com>
To: Ilya Enkovich <enkovich.gnu@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [Boolean Vector, patch 1/5] Introduce boolean vector to be used as a vector comparison type
Date: Wed, 28 Oct 2015 14:57:00 -0000 [thread overview]
Message-ID: <20151028145147.GA14460@arm.com> (raw)
In-Reply-To: <20151002135921.GE26618@msticlxl57.ims.intel.com>
On Fri, Oct 02, 2015 at 02:59:21PM +0100, Ilya Enkovich wrote:
> Hi,
>
> This patch starts the first series to introduce vec<bool> as a vector
> comparison type. This series introduces the new vec<bool> type and force its
> usage for all vector comparisons. This series doesn't intoroduce any new
> vectorization features. I split it into five small patches but will commit
> in a single chunk. Patch series was bootstrapped and tested on
> x86_64-unknown-linux-gnu.
>
> The first patch introduces a target hook and functions to produce new vector
> type.
Hi,
This patch (or whatever combination of patches became r229129) caused an
ICE to show up in my random testing of the AArch64 arm_neon.h intrinsics.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68134
I've tried reproducing the failure on other targets but I can't seem to
get it to trigger elsewhere.
Thanks,
James
---
random-test.c:10:42: internal compiler error: in prepare_cmp_insn, at optabs.c:3820
uint64x1_t result = (uint64x1_t) (arg1 == arg2);
^
0x996e40 prepare_cmp_insn
..../src/gcc/gcc/optabs.c:3820
0x997396 emit_cmp_and_jump_insns(rtx_def*, rtx_def*, rtx_code, rtx_def*, machine_mode, int, rtx_def*, int)
..../src/gcc/gcc/optabs.c:3967
0x72e934 do_compare_rtx_and_jump(rtx_def*, rtx_def*, rtx_code, int, machine_mode, rtx_def*, rtx_code_label*, rtx_code_label*, int)
..../src/gcc/gcc/dojump.c:1149
0x72f52a do_compare_and_jump
..../src/gcc/gcc/dojump.c:1228
0x73134f do_jump_1(tree_code, tree_node*, tree_node*, rtx_code_label*, rtx_code_label*, int)
..../src/gcc/gcc/dojump.c:240
0x731c68 jumpifnot_1(tree_code, tree_node*, tree_node*, rtx_code_label*, int)
..../src/gcc/gcc/dojump.c:148
0x7c6e47 expand_expr_real_2(separate_ops*, rtx_def*, machine_mode, expand_modifier)
..../src/gcc/gcc/expr.c:9030
0x6c5ad9 expand_gimple_stmt_1
..../src/gcc/gcc/cfgexpand.c:3617
0x6c5ad9 expand_gimple_stmt
..../src/gcc/gcc/cfgexpand.c:3677
0x6c8316 expand_gimple_basic_block
..../src/gcc/gcc/cfgexpand.c:5681
0x6cb8c4 execute
..../src/gcc/gcc/cfgexpand.c:6293
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.
prev parent reply other threads:[~2015-10-28 14:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 13:59 Ilya Enkovich
2015-10-09 20:43 ` Jeff Law
2015-10-13 13:17 ` Richard Biener
2015-10-13 13:35 ` Ilya Enkovich
2015-10-13 13:17 ` Ilya Enkovich
2015-10-22 10:24 ` Andreas Schwab
2015-10-22 10:35 ` Ilya Enkovich
2015-10-22 10:51 ` Andreas Schwab
2015-10-22 16:24 ` Ilya Enkovich
2015-10-22 16:45 ` Jeff Law
2015-10-23 9:43 ` Richard Biener
2015-10-23 11:13 ` Ilya Enkovich
2015-10-23 12:57 ` Richard Biener
2015-10-28 13:55 ` Christophe Lyon
2015-10-28 16:54 ` Bill Schmidt
2015-10-28 19:39 ` Ilya Enkovich
2015-10-29 13:13 ` Ilya Enkovich
2015-11-02 19:41 ` Jeff Law
2015-11-03 11:26 ` Richard Biener
2015-11-03 13:42 ` Jeff Law
2015-11-03 16:02 ` Jeff Law
2015-10-28 14:57 ` James Greenhalgh [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=20151028145147.GA14460@arm.com \
--to=james.greenhalgh@arm.com \
--cc=enkovich.gnu@gmail.com \
--cc=gcc-patches@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).