From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 113279 invoked by alias); 25 Jan 2018 17:58:23 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 113270 invoked by uid 89); 25 Jan 2018 17:58:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=no version=3.3.2 spammy=H*Ad:U*patches X-HELO: relay1.mentorg.com Date: Thu, 25 Jan 2018 17:58:00 -0000 From: Joseph Myers To: Palmer Dabbelt CC: , Andrew Waterman , Darius Rad , , Subject: Re: RISC-V glibc port, v5 In-Reply-To: <20180125043621.19972-1-palmer@dabbelt.com> Message-ID: References: <20180125043621.19972-1-palmer@dabbelt.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2018-01/txt/msg00843.txt.bz2 On Wed, 24 Jan 2018, Palmer Dabbelt wrote: > I believe we've taken into account all the feedback, and are now below 20 test Still missing an ldd_rewrite_script setting as mentioned as needed for multi-ABI support in and . The most important thing to figure out at this point - and then stick to (changing your mind after the start of the freeze is not a good way to get a port into 2.27) - is the choice of exactly what architecture and ABI combinations are supported by the port, as that determines what changes are needed to have an internally consistent port without lots of untestable code for unsupported combinations, and a significant proportion of issues from the patch reviews of multiple versions of the RISC-V port have been inconsistencies regarding what is supposed to be supported (especially when the choice has changed between versions of the port, without the changes being carried out consistently through the whole patch series). -- Joseph S. Myers joseph@codesourcery.com