From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/543 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Releasing 0.8.4? Date: Sat, 21 Jan 2012 08:08:47 -0500 Message-ID: <20120121130847.GM132@brightrain.aerifal.cx> References: <20120121010720.GA8353@brightrain.aerifal.cx> <20120121115119.GW31975@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1327152594 21637 80.91.229.12 (21 Jan 2012 13:29:54 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 21 Jan 2012 13:29:54 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-544-gllmg-musl=m.gmane.org@lists.openwall.com Sat Jan 21 14:29:48 2012 Return-path: Envelope-to: gllmg-musl@lo.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by lo.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Rob0t-0000Wl-UA for gllmg-musl@lo.gmane.org; Sat, 21 Jan 2012 14:29:48 +0100 Original-Received: (qmail 29815 invoked by uid 550); 21 Jan 2012 13:29:47 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 29799 invoked from network); 21 Jan 2012 13:29:46 -0000 Content-Disposition: inline In-Reply-To: <20120121115119.GW31975@port70.net> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:543 Archived-At: On Sat, Jan 21, 2012 at 12:51:19PM +0100, Szabolcs Nagy wrote: > * Rich Felker [2012-01-20 20:07:20 -0500]: > > Anything critical that should be addressed before releasing current > > git as 0.8.4? I figure it's been in a "stable" (hiatus) state long > > enough that it should be good, but if not I'd like to hear about the > > problems sooner rather than later. :-) > > i reported a bug about the CHUNK_SIZE macro of malloc The bug I was aware about was fixed. Can you remind me if there's another one I'm not aware about? > there is an old related FIXME comment in malloc.c > you haven't replied my mail if that can be resolved > with the found bug The fix only affected mmapped chunks and the realloc comment was for heap-managed chunks, so unfortunately I don't think it helps. > imho that if(0) can be eliminated > but i don't quite understand the > algorithm as much as you do.. That code also involves a tradeoff (sacrificing a little time for the sake of reducing fragmentation), so it's not 100% clear that it's even desirable. I'd at least like to wait til some time other than right-before-release to study the issue. Rich