From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9197 invoked by alias); 9 Apr 2012 08:17:00 -0000 Received: (qmail 9187 invoked by uid 22791); 9 Apr 2012 08:16:58 -0000 X-SWARE-Spam-Status: No, hits=-4.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED,TW_ZJ 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, 09 Apr 2012 08:16:45 +0000 From: "ubizjak at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/52908] xop-mul-1:f9 miscompiled on bulldozer (-mxop) Date: Mon, 09 Apr 2012 08:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ubizjak at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ubizjak at gmail dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Status Last reconfirmed AssignedTo Ever Confirmed 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-04/txt/msg00533.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52908 Uros Bizjak changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2012-04-09 AssignedTo|unassigned at gcc dot |ubizjak at gmail dot com |gnu.org | Ever Confirmed|0 |1 --- Comment #1 from Uros Bizjak 2012-04-09 08:16:26 UTC --- (In reply to comment #0) > I've no idea how best to solve this, either deactivating the sse4.1 pattern > when TARGET_XOP, or rewriting the latter to not early-clobber result, or > something else entirely. I've tested that the first way fixes this problem. We have attribute enabled for these case. I can take this bug, if you don't mind.