From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21361 invoked by alias); 3 Nov 2011 18:09:21 -0000 Received: (qmail 21350 invoked by uid 22791); 3 Nov 2011 18:09:20 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 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; Thu, 03 Nov 2011 18:09:05 +0000 From: "drepper.fsp at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/50984] New: Boolean return value expression clears register too often Date: Thu, 03 Nov 2011 18:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: drepper.fsp at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: 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: 2011-11/txt/msg00308.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50984 Bug #: 50984 Summary: Boolean return value expression clears register too often Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: drepper.fsp@gmail.com Target: x86_64-linux Compile this code with the current HEAD gcc (or 4.5, I tried that as well) and you see less than optimal code: int f(int a, int b) { return a & 8 && b & 4; } For x86-64 I see this asm code: xorl %eax, %eax andl $8, %edi je .L2 xorl %eax, %eax <----- Unnecessary !!! andl $4, %esi setne %al .L2: rep ret The compiler should realize that the second xor is unnecessary.