public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/62021] ICE in verify_gimple_assign_single
Date: Tue, 05 Aug 2014 13:12:00 -0000 [thread overview]
Message-ID: <bug-62021-4-AAmKC7L6tV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62021-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62021
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. The constructor is built in vectorizable_simd_clone_call
2958 vec_oprnd0 = build_constructor (atype,
ctor_elts);
2959 new_stmt
2960 = gimple_build_assign (make_ssa_name
(atype, NULL),
2961 vec_oprnd0);
(gdb) p debug_generic_expr (atype)
vector(4) float *
huh. The actual elements in the constructor are of type
vector(2) long unsigned int
Seems bestn->simdclone->args[i].vector_type seems to miss that we substitute
integer types for all pointer types in vectors (pointer element vectors are
disallowed)?
next prev parent reply other threads:[~2014-08-05 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 12:25 [Bug tree-optimization/62021] New: " ysrumyan at gmail dot com
2014-08-05 12:28 ` [Bug tree-optimization/62021] " ysrumyan at gmail dot com
2014-08-05 13:12 ` rguenth at gcc dot gnu.org [this message]
2014-08-06 11:48 ` jakub at gcc dot gnu.org
2014-08-06 12:32 ` rguenth at gcc dot gnu.org
2014-12-09 19:24 ` mpolacek at gcc dot gnu.org
2014-12-10 13:38 ` jakub at gcc dot gnu.org
2014-12-10 20:01 ` jakub at gcc dot gnu.org
2014-12-10 20:02 ` jakub at gcc dot gnu.org
2014-12-10 20:18 ` jakub 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-62021-4-AAmKC7L6tV@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).