From patchwork Tue Jan 18 14:37:23 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ramana Radhakrishnan X-Patchwork-Id: 79319 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) by ozlabs.org (Postfix) with SMTP id C5F4FB7116 for ; Wed, 19 Jan 2011 01:37:41 +1100 (EST) Received: (qmail 3762 invoked by alias); 18 Jan 2011 14:37:39 -0000 Received: (qmail 3614 invoked by uid 22791); 18 Jan 2011 14:37:37 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL, BAYES_00, RCVD_IN_DNSWL_LOW, TW_QE X-Spam-Check-By: sourceware.org Received: from service87.mimecast.com (HELO service87.mimecast.com) (94.185.240.25) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Tue, 18 Jan 2011 14:37:31 +0000 Received: from cam-owa1.Emea.Arm.com (fw-tnat.cambridge.arm.com [217.140.96.21]) by service87.mimecast.com; Tue, 18 Jan 2011 14:37:26 +0000 Received: from [10.1.66.29] ([10.1.255.212]) by cam-owa1.Emea.Arm.com with Microsoft SMTPSVC(6.0.3790.0); Tue, 18 Jan 2011 14:37:24 +0000 Subject: [Patch ARM] Fix A9 scheduler . From: Ramana Radhakrishnan Reply-To: ramana.radhakrishnan@arm.com To: gcc-patches@gcc.gnu.org Cc: rearnsha@arm.com Date: Tue, 18 Jan 2011 14:37:23 +0000 Message-Id: <1295361443.679.30.camel@e102325-lin.cambridge.arm.com> Mime-Version: 1.0 X-MC-Unique: 111011814372602001 X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Delivered-To: mailing list gcc-patches@gcc.gnu.org Hi, I've recently discovered that the A9 scheduler was accidentally broken when I committed the neon pipeline description. This fixes this problem and since this is a change in just the backend I would like permission for this to be committed into trunk. Tested with qemu and notice no new regressions. Looking through some simple examples I can now see all parts of the pipeline description now being used correctly. Sorry about the breakage. Ok to commit to trunk ? cheers Ramana 2011-01-11 Ramana Radhakrishnan * config/arm/cortex-a9.md (cortex-a9-neon.md): Actually include. (cortex_a9_dp): Handle neon types correctly. Index: cortex-a9.md =================================================================== --- cortex-a9.md (revision 168633) +++ cortex-a9.md (working copy) @@ -79,9 +79,10 @@ ;; which can go down E2 without any problem. (define_insn_reservation "cortex_a9_dp" 2 (and (eq_attr "tune" "cortexa9") - (ior (eq_attr "type" "alu") - (ior (and (eq_attr "type" "alu_shift_reg, alu_shift") - (eq_attr "insn" "mov")) + (ior (and (eq_attr "type" "alu") + (eq_attr "neon_type" "none")) + (and (and (eq_attr "type" "alu_shift_reg, alu_shift") + (eq_attr "insn" "mov")) (eq_attr "neon_type" "none")))) "cortex_a9_p0_default|cortex_a9_p1_default") @@ -263,3 +264,6 @@ (and (eq_attr "tune" "cortexa9") (eq_attr "type" "fdivd")) "ca9fp_ds1 + ca9_issue_vfp_neon, nothing*24") + +;; Include Neon pipeline description +(include "cortex-a9-neon.md")