From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 29848 invoked from network); 1 May 2023 19:41:39 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 1 May 2023 19:41:39 -0000 Received: (qmail 7838 invoked by uid 550); 1 May 2023 19:41:37 -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 7806 invoked from network); 1 May 2023 19:41:35 -0000 Date: Mon, 1 May 2023 15:41:21 -0400 From: Rich Felker To: =?utf-8?B?SuKCkeKCmeKCmw==?= Gustedt Cc: musl@lists.openwall.com Message-ID: <20230501194121.GS4163@brightrain.aerifal.cx> References: <20230501205037.29e42745@inria.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20230501205037.29e42745@inria.fr> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] patches for C23 On Mon, May 01, 2023 at 08:50:37PM +0200, Jā‚‘ā‚™ā‚› Gustedt wrote: > Hello, > I now have a series of patches (~40) that implement most the missing > bits for C23 support. Nothing is very deep, here, I think, but > probably that is still quite a chunk to review. They are compile > tested for gcc version 7 to 12 and clang versions 9 to 17, but only on > x86_64. > > Shall I sent them all here (I would have to refresh my git skills for > that) or does somebody want to browse on some sort of gitlab host > first? > > When implementing this I also marginally updated my page describing > C23 library changes > > https://gustedt.gitlabpages.inria.fr/c23-library/ If you want discussion of them, it would be most helpful to submit as attachments to the list where the context of discussion will exist in immutable form, rather than as a git branch that might disappear or be replaced. ~40 is a lot for attachments to a single message, but ~40 individual posts would also be overwhelming, so it probably makes sense to group them by areas of functionality or layering or something. Likely there are going to be a bunch that are fairly uncontroversial and mechanical, and some that are more invasive and that will attract more meaningful discussion. Rich