From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19044 invoked by alias); 6 Jan 2007 17:47:15 -0000 Received: (qmail 19015 invoked by uid 48); 6 Jan 2007 17:47:05 -0000 Date: Sat, 06 Jan 2007 17:47:00 -0000 Message-ID: <20070106174705.19014.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/24659] Conversions are not vectorized In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "ubizjak at gmail dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-01/txt/msg00411.txt.bz2 ------- Comment #6 from ubizjak at gmail dot com 2007-01-06 17:47 ------- (In reply to comment #2) > vectorization of type conversions has recently been added to autovect-branch. > It requires modeling the respective unpack and pack optabs in the machine > description. Hm, there is no infrastructure for int<->float conversions. vectorizable_operation() calls optab_for_tree_code() with "code" argument set to FLOAT_EXPR and FIX_TRUNC_EXPR and these always return NULL. In DFmode<->SFmode case, vectorizable_operation() calls optab_for_tree_code() with VEC_PACK_MOD_EXPR and VEC_UNPACK_LO/HI_EXPR. At least the later case is intended for integer modes, as optab_for_tree_code() checks for TYPE_UNSIGNED on "type" argument. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24659