Issues remaining for release?

Issues remaining for release?

[Rich Felker]

Hi all,

Are there any major issues left that should be resolved before a
release? I know there are small things (like remaining syscall
wrappers) that will continue to trickle in while we hold off for some
testing of the big changes, but I think all the big stuff for the next
release is done.

Scheduling priority related stuff will almost surely wait for the next
release cycle now. Real setvbuf still could be done now or later, but
I'm not sure if it's useful enough to spend effort right now on making
sure it's done correctly.

Major changes since the last release so far include:
- Default features w/no feature test macros
- C89 compatibility in header
- Many header fixes
- C99 restrict keyword usage
- GNU hash support in dynamic linker
- dladdr support
- Dynamic linker multiple error reporting
- Fixed broken atexit
- Lots of header bugfixes
- Partial C11 support
- SHA 256/512 hashes
- Support for many/most newer Linux syscalls
- Better support for compiling musl with clang or other compilers
- Major debloating of ARM and MIPS syscall routines.

Since many of these are fairly invasive, it'd be great to have some
help testing for regressions.

Rich

Re: Issues remaining for release?

[John Spencer]

On 09/11/2012 08:45 AM, Rich Felker wrote:
> Hi all,
>
> Are there any major issues left that should be resolved before a
> release?
no
> Since many of these are fairly invasive, it'd be great to have some
> help testing for regressions.
>
no regressions detected while doing a full sabotage amd64 build with 
latest git.
since the mips and arm port was never widely used, i think it's safe to 
get out a release.
(doing a full build on arm would take about 2 days, so i refrained from 
doing so for the moment.)