From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3962 invoked by alias); 23 Dec 2010 01:56:42 -0000 Received: (qmail 3783 invoked by uid 22791); 23 Dec 2010 01:56:41 -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, 23 Dec 2010 01:56:36 +0000 From: "hp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/45051] [4.6 Regression]: gcc.c-torture/execute/builtins/abs-2.c and abs-3.c due to "track subwords of DImode allocnos" X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: hp at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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 Date: Thu, 23 Dec 2010 01:56:00 -0000 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: 2010-12/txt/msg02529.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45051 --- Comment #8 from Hans-Peter Nilsson 2010-12-23 01:56:08 UTC --- (In reply to comment #7) > (insn 3163 3161 3164 107 rectmm.c:1041 (set (reg:SI 1 r1) > (plus:SI (reg:SI 1 r1) > (const_int 280 [0x118]))) 4 {*arm_addsi3} (nil)) > I think the issue might be that reg_mentioned_p() considers output registers to > have been "mentioned", whereas the refers_to_regno_p() does not consider an > output register to have been "referred to". But r1 is an input as well as an output , i.e. "referred to", so insn 3163 should have matched without your patch. I'm missing analysis on why that didn't happen. Nevertheless, I'm testing r162418 with your patch. Also, you should open a separate PR for the regression you see, not just reuse this one. Use the depends-on features for the dependency.