From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30004 invoked by alias); 9 Sep 2013 21:02:14 -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 29991 invoked by uid 89); 9 Sep 2013 21:02:14 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 09 Sep 2013 21:02:14 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r89L24SJ023687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Sep 2013 17:02:04 -0400 Received: from [10.3.113.46] (ovpn-113-46.phx2.redhat.com [10.3.113.46]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r89L22wd001963; Mon, 9 Sep 2013 17:02:03 -0400 Message-ID: <522E374A.7060006@redhat.com> Date: Mon, 09 Sep 2013 21:02:00 -0000 From: "Carlos O'Donell" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130805 Thunderbird/17.0.8 MIME-Version: 1.0 To: "Joseph S. Myers" CC: Will Newton , "libc-ports@sourceware.org" , Patch Tracking Subject: Re: [PATCH v3] ARM: Improve armv7 memcpy performance. References: <522D977E.2000906@linaro.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2013-09/txt/msg00074.txt.bz2 >> These are all surmountable problems but I would rather not gate >> acceptance of this code on a satisfactory resolution of the above >> issues. I can provide output from the cortex-strings benchmark quite >> instead though. > > If your summary of the benchmarking discussion indicates that the existing > glibc benchmark is not relevant for the cases addressed by the patch, then > it's indeed appropriate to give such results from another benchmark. Agreed. Cheers, Carlos.