From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 125802 invoked by alias); 1 Mar 2016 19:02:41 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 125689 invoked by uid 89); 1 Mar 2016 19:02:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=H*r:15.1.427, disparaged, f_mcr, H*RU:15.1.427.16 X-HELO: eu-smtp-delivery-143.mimecast.com Received: from eu-smtp-delivery-143.mimecast.com (HELO eu-smtp-delivery-143.mimecast.com) (207.82.80.143) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 01 Mar 2016 19:02:36 +0000 Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lrp0080.outbound.protection.outlook.com [213.199.154.80]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-30-l5VyZILtRJ23-sWfTYOEDQ-1; Tue, 01 Mar 2016 19:02:30 +0000 Received: from AM3PR08MB0088.eurprd08.prod.outlook.com (2a01:111:e400:8847::18) by AM3PR08MB0593.eurprd08.prod.outlook.com (2a01:111:e400:c408::15) with Microsoft SMTP Server (TLS) id 15.1.427.16; Tue, 1 Mar 2016 19:02:29 +0000 Received: from AM3PR08MB0088.eurprd08.prod.outlook.com ([fe80::5c9e:21ac:62e:8faa]) by AM3PR08MB0088.eurprd08.prod.outlook.com ([fe80::5c9e:21ac:62e:8faa%17]) with mapi id 15.01.0415.022; Tue, 1 Mar 2016 19:02:29 +0000 From: Wilco Dijkstra To: Evandro Menezes CC: "gcc-patches@gcc.gnu.org" , nd , Marcus Shawcroft , Kyrylo Tkachov , James Greenhalgh Subject: Re: [PATCH][AArch64] Replace insn to zero up DF register Date: Tue, 01 Mar 2016 19:02:00 -0000 Message-ID: References: <56A94F35.8000000@samsung.com> <56D0D50E.8030802@samsung.com> ,<56D4D02C.6030309@samsung.com> In-Reply-To: <56D4D02C.6030309@samsung.com> x-ms-office365-filtering-correlation-id: e095b4f1-52bf-467f-268f-08d34204098b x-microsoft-exchange-diagnostics: 1;AM3PR08MB0593;5:isc2Jj05ljHgxO8hFQs67R+u/Tq5bbohn8SJmL4MhHleXHTVIYzVoUFpYu8DM7GqhHzeNPF1+BpqBb+6jnnjWltTKufKldUzfpJoA1GjLTNWAGCC+vNuL38jGIrW3ZynGxdS15ohaWRdHXrqobhp/A==;24:nSS2oFwgJVPDK4fWORTvf3s2L3SdVVfzumWekmKI5Q1oLs3h5V0SWa0UlLkt/OhrEaHjyVquphZ3rGW9LiDp1lEqTKLEO9DTlposKYqvf2o=;20:Q9grzZlTRG1tkkMLiAaCaA2FWtagqcdYl3feq8aCztUvRNPAVKMkTUibr+QvBPqFK+DzU71WSjL8maUX9vz+qVukN6gwQ2tc98KWQ8ThnDoFf2Wrax940EoLn3Oxfk+NyG+Txg5gr5VKni7L/0YNw5i9IU2HgxmQtXMWC0jr4Y4= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM3PR08MB0593; nodisclaimer: True x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046);SRVR:AM3PR08MB0593;BCL:0;PCL:0;RULEID:;SRVR:AM3PR08MB0593; x-forefront-prvs: 086831DFB4 x-forefront-antispam-report: SFV:NSPM;SFS:(10009020)(6009001)(24454002)(50986999)(76176999)(3660700001)(5001960100004)(81156009)(11100500001)(3846002)(87936001)(110136002)(3280700002)(1220700001)(586003)(102836003)(1096002)(4326007)(189998001)(5250100002)(2906002)(6116002)(2900100001)(76576001)(2950100001)(5002640100001)(92566002)(5003600100002)(86362001)(54356999)(5008740100001)(93886004)(66066001)(40100003)(74316001)(106116001)(33656002);DIR:OUT;SFP:1101;SCL:1;SRVR:AM3PR08MB0593;H:AM3PR08MB0088.eurprd08.prod.outlook.com;FPR:;SPF:None;MLV:sfv;LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: arm.com X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Mar 2016 19:02:29.4288 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR08MB0593 X-MC-Unique: l5VyZILtRJ23-sWfTYOEDQ-1 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable X-SW-Source: 2016-03/txt/msg00073.txt.bz2 Evandro Menezes wrote: > > The meaning of these attributes are not clear to me. Is there a > reference somewhere about which insns are FP or SIMD or neither? The meaning should be clear, "fp" is a floating point instruction, "simd" a= SIMD one as defined in ARM-ARM. > Indeed, I had to add the Y for the f_mcr insn to match it with nosimd. > However, I didn't feel that it should be moved to the right, since it's > already disparaged. Am I missing something detail? It might not matter for this specific case, but I have seen reload forcing = the very first alternative without looking at any costs or preferences - as long as = it is legal. This suggests we need to order alternatives from most preferred alternative= to least preferred one. I think it is good enough for commit, James? Wilco