public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49536] New: latent bug in FSF gcc with creation of vector of arrays
Date: Sun, 26 Jun 2011 22:45:00 -0000 [thread overview]
Message-ID: <bug-49536-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49536
Summary: latent bug in FSF gcc with creation of vector of
arrays
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: howarth@nitro.med.uc.edu
Duncan Sands has determined that http://llvm.org/bugs/show_bug.cgi?id=10042
exposes a bug in FSF gcc where vectors of arrays are being created. He proposes
that the following patch to FSF gcc exposes the latent issue...
Index: tree-vect-data-refs.c
===================================================================
--- tree-vect-data-refs.c (revision 174743)
+++ tree-vect-data-refs.c (working copy)
@@ -2734,6 +2734,10 @@
scalar_type = TREE_TYPE (DR_REF (dr));
STMT_VINFO_VECTYPE (stmt_info) =
get_vectype_for_scalar_type (scalar_type);
+ gcc_assert(!STMT_VINFO_VECTYPE (stmt_info) ||
+ TREE_CODE (STMT_VINFO_VECTYPE (stmt_info)) != VECTOR_TYPE ||
+ TREE_CODE (TREE_TYPE (STMT_VINFO_VECTYPE (stmt_info)))
+ != ARRAY_TYPE);
if (!STMT_VINFO_VECTYPE (stmt_info))
{
if (vect_print_dump_info (REPORT_UNVECTORIZED_LOCATIONS))
by triggering an assertion failure when the tree-vectorizer tries to form a
vector of arrays.
next reply other threads:[~2011-06-26 22:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 22:45 howarth at nitro dot med.uc.edu [this message]
2011-06-27 7:46 ` [Bug middle-end/49536] " baldrick at gcc dot gnu.org
2011-06-27 8:43 ` [Bug middle-end/49536] latent bug " ebotcazou at gcc dot gnu.org
2011-06-27 9:10 ` [Bug middle-end/49536] latent bug in FSF gcc " rguenth at gcc dot gnu.org
2011-06-27 10:32 ` [Bug middle-end/49536] latent bug " rguenth at gcc dot gnu.org
2011-06-27 10:33 ` rguenth at gcc dot gnu.org
2011-06-27 16:32 ` howarth at nitro dot med.uc.edu
2011-06-27 17:10 ` howarth at nitro dot med.uc.edu
2012-02-10 12:34 ` baldrick 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-49536-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).