Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 21 Jan 2019 14:03:16 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: musl 1.1.21 released

On Mon, Jan 21, 2019 at 10:37:08AM -0800, Khem Raj wrote:
> Hi Rich
> 
> Great news ! will you also create a git tag for it ?
> 
> I dont see it here
> 
> https://git.musl-libc.org/cgit/musl

Just hadn't pushed. It should be there now.

> On Mon, Jan 21, 2019 at 10:18 AM Rich Felker <dalias@...c.org> wrote:
> >
> > This release makes improvements with respect to default thread stack
> > size, including increasing the default from 80k to 128k, increasing
> > the default guard size from 4k to 8k, and allowing the default to be
> > increased via ELF headers so that programs that need larger stacks can
> > be build without source-level changes, using just LDFLAGS.
> > Insufficient stack size for AIO threads on kernels that don't honor
> > the constant MINSIGSTKSZ is also fixed.
> >
> > The glob core has been rewritten to fix inability to see past
> > searchable-but-unreadable path components, and to avoid excessive
> > stack usage and unnecessary syscalls. The tsearch AVL tree
> > implementation has also been rewritten for better size and
> > performance. The math library adds more native single-instruction
> > implementations for arm, s390x, powerpc, and x86_64.
> >
> > Various bugs are fixed, including several possible deadlocks, one of
> > which was a new regression in 1.1.20.
> >
> >
> > https://www.musl-libc.org/releases/musl-1.1.21.tar.gz
> > https://www.musl-libc.org/releases/musl-1.1.21.tar.gz.asc
> >
> >
> >
> >
> > Special thanks to musl's release sponsors (patreon.com/musl):
> >
> > * Justin Cormack
> > * Laurent Bercot
> > * Les Aker
> > * Neal Gompa
> > * Hurricane Labs (hurricanelabs.com)
> > * The Midipix Project (midipix.org)

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.