public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ysrumyan at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/62021] New: ICE in verify_gimple_assign_single
Date: Tue, 05 Aug 2014 12:25:00 -0000 [thread overview]
Message-ID: <bug-62021-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62021
Bug ID: 62021
Summary: ICE in verify_gimple_assign_single
Product: gcc
Version: 4.10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: ysrumyan at gmail dot com
For attached simple test-case if we omit 'uniform' specification compiler
produces ICE:
error: incorrect type of vector CONSTRUCTOR elements
Note that for stmt
_38 = {vect_cst_.62_39, vect_cst_.62_39};
we have type mismatch - type of rhs constructor element is vector(2) long
unsigned int whereas type of lhs is vector(4) float*.
If we add 'uniform' specification (through -DUNIFORM option) test compiles
successfully. I assume that ICE must be fixed.
next reply other threads:[~2014-08-05 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 12:25 ysrumyan at gmail dot com [this message]
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
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@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).