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 middle-end/49536] latent bug in FSF gcc with creation of vector of arrays
Date: Mon, 27 Jun 2011 09:10:00 -0000 [thread overview]
Message-ID: <bug-49536-4-7yXwjIxSZQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49536-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49536
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2011.06.27 09:09:35
AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org
|gnu.org |
Summary|latent bug with creation of |latent bug in FSF gcc with
|vector of arrays |creation of vector of
| |arrays
Ever Confirmed|0 |1
--- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-06-27 09:09:35 UTC ---
Confirmed. I also get into the issue that get_vectype_for_scalar_type_and_size
is called with a vector typed scalar_type (from basic-block vectorization).
Your case ends up with character(kind=1)[1:4] which has SImode.
The issue is that we really would only care for the component mode
(and we make sure it is either int or float mode), but not really for
what type it does represent (I can imagine we'll happily create a
vector type of RECORD_TYPE components this way).
Nothing on the GIMPLE level is prepared for non-scalar types here
though, so I'm not sure what issues we run into with this right now.
OTOH vectorization will very likely fail later anyway if we are not
only presented with a memory copy loop. So, for gimple hygiene
we should reject component types we cannot easily handle.
next prev parent reply other threads:[~2011-06-27 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 22:45 [Bug middle-end/49536] New: " howarth at nitro dot med.uc.edu
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 ` rguenth at gcc dot gnu.org [this message]
2011-06-27 10:32 ` 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-7yXwjIxSZQ@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).