From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14655 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: ARM Cortex-M FDPIC ABI Date: Wed, 11 Sep 2019 10:29:03 -0400 Message-ID: <20190911142903.GX9017@brightrain.aerifal.cx> References: <20190911141944.GW9017@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="116893"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-14671-gllmg-musl=m.gmane.org@lists.openwall.com Wed Sep 11 16:29:19 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1i83cU-000UHI-Ly for gllmg-musl@m.gmane.org; Wed, 11 Sep 2019 16:29:18 +0200 Original-Received: (qmail 3781 invoked by uid 550); 11 Sep 2019 14:29:16 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 3759 invoked from network); 11 Sep 2019 14:29:15 -0000 Content-Disposition: inline In-Reply-To: <20190911141944.GW9017@brightrain.aerifal.cx> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:14655 Archived-At: On Wed, Sep 11, 2019 at 10:19:44AM -0400, Rich Felker wrote: > On Wed, Sep 11, 2019 at 05:08:57PM +0300, Alexandru Onea wrote: > > Dear musl developers, > > > > I am reading in the roadmap [1] that musl 1.1.26 introduces the ARM FDPIC > > ABI, which is great news. Is there a development branch / snapshot > > including this feature, which I can use for experimental work? > > > > [1] https://wiki.musl-libc.org/roadmap.html#musl-1.1.26 > > Roadmap is intent for future development, not secret branches that are > already finished. :-) > > (Well, the switchover to time64 is kinda such a branch, but the > patches have been posted on the list.) And to clarify *why* time64 switchover is just patches posted to the list, rather than a public git branch, it's because this is a matter of defining future ABI, and I really don't want to be giving ppl the impression that using them in their current state is something reasonable to do. Doing so would almost surely end up with binaries that mismatch with the final ABI, probably in subtle ways that go unnoticed until something catastrophic happens. Rich