From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.2 Received: from mother.openwall.net (mother.openwall.net [195.42.179.200]) by inbox.vuxu.org (OpenSMTPD) with SMTP id 8fee2769 for ; Wed, 22 Jan 2020 00:48:08 +0000 (UTC) Received: (qmail 21655 invoked by uid 550); 22 Jan 2020 00:48:07 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 21637 invoked from network); 22 Jan 2020 00:48:06 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=v0u7zVgd5uDcjPQn0DvxHfIDKm9uuEFGUyNB2XPEM20=; b=WAPbDf/FriLSaearOkpRRSC/Myc49mf6EGH7itDx8AezvFEIMsgTdZOiB4E5RRcJxU tqkfbsZXy3IuINiiv9tSd4Vcy7I9cnicYk/ZBWWoBCAYNWoWrlPTILwqOP7H7YtUzN62 0wCBP6UGyQtQNrrmSD7PHEh8OWT6dLji9uVLnXyoiiR22AKdslZ+yg/Ieb8XnJWZ1ygQ 6jeQBaeVgrNTZendAvxrl8e/yssXQxcBHhlk8vYRceCD313h/If/DE3Pf3gE98IJNglA /u77oB95wymn1La8P/UXXSgm/gPpuejQ5eIP3wmnYIS3uDXmhLkn9N2NbPa1nfAMdqvj hw0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=v0u7zVgd5uDcjPQn0DvxHfIDKm9uuEFGUyNB2XPEM20=; b=q7lOQMlj1PvTg98btZfXK/9CYj977mI7Z5EInhqKoz5PeH6s5FBt2wDW+zuo5cjx0n EokHgqXcuAxNfUtCJPK9dqY/uj7BIXWu3+qeJ0IAeUWHFxj23GguE5FLSHa8ypUubdMH GqXyOFKcO7ozevBg51K/VNjrM15WqKxxakNyxKFCWgrM0SrmloMLbSFGDwxqf92px83d Y97tBhGlfCOXp2beZ9sbG3hByMqA+fkB8AUv8YoBWITjgcNUX7jTHyz7bXSgAhauCpzo ZuUNlJqYNlMuAyGo+wAevC2QXVTRwSLKBLO0+TIracOivMlMXITOZAvL116anSrXRF6o SW1g== X-Gm-Message-State: APjAAAXnciz/AJLdbVJAchq2qgQ7khWnnLznMN1tfuu29fDQ8jYveW7Y BVfVUYfdFop0DNYycmFx2c+q5PLftmSQOgudWEFLSg== X-Google-Smtp-Source: APXvYqxpGr3AlC/SvCtBjgH+VERwXu4zxmKIDI4Xzs0mtJwDhAeLj6BRrzYwIjV7/v0MHH9IEYjGkLiZJGwmPjL2oe4= X-Received: by 2002:a67:ee4e:: with SMTP id g14mr986123vsp.223.1579654074130; Tue, 21 Jan 2020 16:47:54 -0800 (PST) MIME-Version: 1.0 References: <20200121185215.5958-1-armccurdy@gmail.com> <20200122003615.GV30412@brightrain.aerifal.cx> In-Reply-To: <20200122003615.GV30412@brightrain.aerifal.cx> From: Andre McCurdy Date: Tue, 21 Jan 2020 16:47:42 -0800 Message-ID: To: musl@lists.openwall.com Content-Type: text/plain; charset="UTF-8" Subject: Re: [musl] [PATCH v2] Add big-endian support to ARM assembler memcpy On Tue, Jan 21, 2020 at 4:36 PM Rich Felker wrote: > On Tue, Jan 21, 2020 at 10:52:15AM -0800, Andre McCurdy wrote: > > Allow the existing ARM assembler memcpy implementation to be used for > > both big and little endian targets. > > --- > > > > Exactly the same changes as before but rebased to account for > > whitespace changes in the preceding patch to add Thumb2 support. > > Thanks. I'm not sure if I'll ever apply this, since I think there's a > better memcpy we may be adopting, but it's nice to have in case we > want to. OK. Slightly disappointed to hear that. I've already been carrying this patch for many months in my own builds so hopefully the new memcpy() which will allow it to be dropped is imminent!