From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by sourceware.org (Postfix) with ESMTP id 6BCE6386180A for ; Tue, 8 Dec 2020 13:31:07 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 6BCE6386180A Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id F38E630E; Tue, 8 Dec 2020 05:31:06 -0800 (PST) Received: from [192.168.1.19] (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 7FA113F718; Tue, 8 Dec 2020 05:31:06 -0800 (PST) Subject: Re: [PATCH] aarch64: Add ILP32 ABI support in assembly To: Sebastian Huber , newlib@sourceware.org References: <20201201183107.17039-1-kinsey.moore@oarcorp.com> From: Richard Earnshaw Message-ID: Date: Tue, 8 Dec 2020 13:31:05 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3492.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: newlib@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Newlib mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Dec 2020 13:31:11 -0000 On 08/12/2020 13:13, Sebastian Huber wrote: > Hello Richard, > > On 08/12/2020 13:27, Richard Earnshaw via Newlib wrote: >> 2) I'd really prefer that this change were made first to the Arm >> Optimized Routines repository; we can then sync the fixed/updated >> versions from there into newlib and avoid fragmentation or potential >> merge issues in future by doing that. > > is > > https://github.com/ARM-software/optimized-routines > > also the right place to address issues with the Cortex-R52 support? > Yes. Thanks, R.