From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9617 invoked by alias); 18 Jun 2013 22:44:43 -0000 Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org Received: (qmail 9607 invoked by uid 89); 18 Jun 2013 22:44:43 -0000 X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,TW_CP autolearn=ham version=3.3.1 Received: from toast.topped-with-meat.com (HELO topped-with-meat.com) (204.197.218.159) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 18 Jun 2013 22:44:42 +0000 Received: by topped-with-meat.com (Postfix, from userid 5281) id B670C2C0E4; Tue, 18 Jun 2013 15:44:40 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: "Joseph S. Myers" Cc: Subject: Re: [PATCH roland/arm-memcpy] ARM: Make armv7 memcpy implementations SFI-friendly In-Reply-To: Joseph S. Myers's message of Tuesday, 18 June 2013 22:20:17 +0000 References: <20130618220149.CB94E2C0E4@topped-with-meat.com> Message-Id: <20130618224440.B670C2C0E4@topped-with-meat.com> Date: Tue, 18 Jun 2013 22:44:00 -0000 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=LYSvtFvi c=1 sm=1 tr=0 a=WkljmVdYkabdwxfqvArNOQ==:117 a=14OXPxybAAAA:8 a=j2EJk06AWKsA:10 a=Z6MIti7PxpgA:10 a=kj9zAlcOel0A:10 a=hOe2yjtxAAAA:8 a=PsDfrxlol9kA:10 a=CCpqsmhAAAAA:8 a=LWyV5zomNRGOalfrhN8A:9 a=CjuIK1q_8ugA:10 X-SW-Source: 2013-06/txt/msg00037.txt.bz2 > This is OK with the comments referring to an assembler bug amended to give > a binutils bug number (and preferably an indication of for what version it > was fixed) to make it easier in future to tell whether the workaround can > be removed because of a higher minimum binutils version requirement. Committed. The comment now says: /* These need an extra layer of macro just to work around a bug in the assembler's parser when an operand starts with a {...}. http://sourceware.org/bugzilla/show_bug.cgi?id=15647 tracks that bug; it was not fixed as of binutils-2.23.2. */ The fix is waiting for a binutils maintainer's review. I expect it will be in 2.24 and in 2.23.3 if there is ever a 2.23.3, but it's not resolved yet. Thanks, Roland