From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13711 invoked by alias); 27 Nov 2006 11:19:56 -0000 Received: (qmail 13683 invoked by uid 48); 27 Nov 2006 11:19:45 -0000 Date: Mon, 27 Nov 2006 11:19:00 -0000 Message-ID: <20061127111945.13682.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/22372] Vectorizer produces mis-match types In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "irar at il dot ibm 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: 2006-11/txt/msg02337.txt.bz2 ------- Comment #5 from irar at il dot ibm dot com 2006-11-27 11:19 ------- The patch I committed (comment #4) fixes almost all the type mismatch occurrences in the vectorizer, but there's one occurrence that still remains - one of the vectorizer testcases (vect-reduc-dot-u8b.c) still fails with modify.diff.txt on MODIFY_EXPR where the right hand side is a call to a builtin function (rs6000_builtin_mul_widen_even). For Altivec, the return value of the builtin function is always signed (while the left hand side of the assignment is unsigned). Is the check in modify.diff.txt too strict or is the problem with the return type of the Altivec builtin (shouldn't it be signed/unsigned as relevant, instead of always signed? Specifically - shouldn't builtin vmuloub return an unsigned type)? Ira -- irar at il dot ibm dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |irar at il dot ibm dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22372