From ccbf5bb4ae76e65ed466384fe0f087b262b8f809 Mon Sep 17 00:00:00 2001 From: Richard Guenther Date: Mon, 27 Jun 2011 10:31:30 +0000 Subject: [PATCH] re PR middle-end/49536 (latent bug with creation of vector of arrays) 2011-06-27 Richard Guenther PR tree-optimization/49536 * tree-vect-stmts.c (get_vectype_for_scalar_type_and_size): For non-scalar inner types use a scalar type according to the scalar inner mode. From-SVN: r175475 --- gcc/ChangeLog | 7 +++++++ gcc/tree-vect-stmts.c | 9 +++++++++ 2 files changed, 16 insertions(+) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 4a8cf00e4f1..b6e12f14b3a 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,10 @@ +2011-06-27 Richard Guenther + + PR tree-optimization/49536 + * tree-vect-stmts.c (get_vectype_for_scalar_type_and_size): + For non-scalar inner types use a scalar type according to + the scalar inner mode. + 2011-06-27 Richard Guenther PR tree-optimization/49365 diff --git a/gcc/tree-vect-stmts.c b/gcc/tree-vect-stmts.c index f9b96391081..8ac21255662 100644 --- a/gcc/tree-vect-stmts.c +++ b/gcc/tree-vect-stmts.c @@ -5350,6 +5350,15 @@ get_vectype_for_scalar_type_and_size (tree scalar_type, unsigned size) && GET_MODE_CLASS (inner_mode) != MODE_FLOAT) return NULL_TREE; + /* We shouldn't end up building VECTOR_TYPEs of non-scalar components. + When the component mode passes the above test simply use a type + corresponding to that mode. The theory is that any use that + would cause problems with this will disable vectorization anyway. */ + if (!SCALAR_FLOAT_TYPE_P (scalar_type) + && !INTEGRAL_TYPE_P (scalar_type) + && !POINTER_TYPE_P (scalar_type)) + scalar_type = lang_hooks.types.type_for_mode (inner_mode, 1); + /* If no size was supplied use the mode the target prefers. Otherwise lookup a vector mode of the specified size. */ if (size == 0) -- 2.30.2