From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23373 invoked by alias); 30 Jul 2012 08:47:52 -0000 Received: (qmail 23355 invoked by uid 22791); 30 Jul 2012 08:47:51 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 30 Jul 2012 08:47:36 +0000 From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/53773] Vectorizer generates non-canonical multiplies Date: Mon, 30 Jul 2012 08:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: wschmidt at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.8.0 X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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: 2012-07/txt/msg02125.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53773 --- Comment #6 from rguenther at suse dot de 2012-07-30 08:47:35 UTC --- On Sun, 29 Jul 2012, wschmidt at gcc dot gnu.org wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53773 > > William J. Schmidt changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > AssignedTo|unassigned at gcc dot |wschmidt at gcc dot gnu.org > |gnu.org | > Target Milestone|--- |4.8.0 > > --- Comment #5 from William J. Schmidt 2012-07-29 16:54:45 UTC --- > I'll take this one. > > I think the assumption of operand placement is too embedded to tease out > easily, so I'm going to approach this by re-canonicalizing PLUS_EXPR, > POINTER_PLUS_EXPR, and MULT_EXPR when operand swapping has occurred. Are there > other tree codes that could be broken? I don't think so