|Deletions are marked like this.||Additions are marked like this.|
|Line 89:||Line 89:|
| * New POSIX-compliance '''fmemopen'''
* [[https://sourceware.org/ml/libc-alpha/2014-06/msg00918.html|Add x86 32 bit vDSO time function support]]
* Transactional Lock Elision for PowerPC:
1. Current status
The release branch of glibc-2.21 is maintained by USER (USER@EMAIL) and its current release is 2.21.0, tagged on DATE. There are no immediate plans for the next release.
The ref structure of this branch is:
- release/2.21/master: main branch
- glibc-2.21.N: revision releases tagged out of release/2.21/master
These people are interested in contents and further revisions tagged on the branch:
The general policies for release branches apply to this branch. Do you think a certain bugfix should be included in this branch?
- Is the fix committed in master? It has to be, unless it's not applicable to master (e.g. code has been rewritten meantime).
- Do you have commit permissions? If so, go ahead if you think it's reasonably safe. break;
- Can you handle Git yourself? Then you can clone the glibc repository, cherry-pick the appropriate fixes, push your branch out and send a pull request at libc-alpha. break;
- Add the glibc_2.21 keyword to the appropriate bug report.
- If there is no appropriate bug report, send a request for the fix to be included to libc-alpha.
A revision release is tagged either when some critical bug-fix appears, or after some period of real-world testing, usually mainly in some SUSE distribution branch (but other distributions are welcome to run latest release/2.21/master as well, more so if they tell me about it!).
What things do we want to accomplish this release?
2.1. Release blockers?
- Make -Wundef into an error.
- Finish -Wundef cleanup: no -Wundef warnings in build on any supported configuration. Consolidated list of outstanding warnings on i386 and x86_64 follows. Other architectures may have other outstanding warnings that are not covered here:
167 IS_IN_libc 171 IS_IN_libc 1 ABI_libm_GLIBC_2_19 3 HAVE_IFUNC 5 MMAP2_PAGE_SHIFT 2 _POSIX_BASE 2 _POSIX_C_LANG_SUPPORT 2 _POSIX_C_LANG_SUPPORT_R 2 _POSIX_DEVICE_IO 2 _POSIX_DEVICE_SPCIFIC 2 _POSIX_DEVICE_SPCIFIC_R 2 _POSIX_FD_MGMT 2 _POSIX_FIFO 2 _POSIX_FILE_ATTRIBUTES 2 _POSIX_FILE_LOCKING 2 _POSIX_FILE_SYSTEM 2 _POSIX_MULTI_PROCESS 2 _POSIX_NETWORKING 2 _POSIX_PII 2 _POSIX_PII_INTERNET 2 _POSIX_PII_INTERNET_DGRAM 2 _POSIX_PII_INTERNET_STREAM 2 _POSIX_PII_OSI 2 _POSIX_PII_OSI_CLTS 2 _POSIX_PII_OSI_COTS 2 _POSIX_PII_OSI_M 2 _POSIX_PII_SOCKET 2 _POSIX_PII_XTI 2 _POSIX_PIPE 2 _POSIX_POLL 2 _POSIX_REGEX_VERSION 2 _POSIX_SELECT 2 _POSIX_SINGLE_PROCESS 2 _POSIX_SYSTEM_DATABASE 2 _POSIX_SYSTEM_DATABASE_R 2 _POSIX_USER_GROUPS 2 _POSIX_USER_GROUPS_R 5 _POSIX_V6_ILP32_OFFBIG 5 _POSIX_V6_LP64_OFF64 5 _POSIX_V6_LPBIG_OFFBIG 5 _POSIX_V7_LPBIG_OFFBIG 5 _XBS5_ILP32_OFF32 5 _XBS5_ILP32_OFFBIG 5 _XBS5_LP64_OFF64 5 _XBS5_LPBIG_OFFBIG 7 _POSIX_V6_ILP32_OFF32 9 _POSIX_V7_ILP32_OFF32 9 _POSIX_V7_ILP32_OFFBIG 9 _POSIX_V7_LP64_OFF64 9 __ASSUME_IPC64
- All _POSIX_* and _XBS_* warnings ought to have a single fix.
New POSIX-compliance fmemopen
- Transactional Lock Elision for PowerPC:
2.2. Desirable this release?
3. Known Issues
3.1. Build and test issues
Describe build and test issues for each architecture, or confirm a clean build with no testsuite failures. The list below is not a complete list of ABI variants; testing should try to cover the different ABI variants as far as possible.
Build system: UNAME -a, GCC?, Binutils?, Kernel ?
TRIMMED LIST OF FAILURES.
3.1.10. PowerPC (32-bit soft-float)
3.1.11. PowerPC (32-bit hard-float)
3.1.12. PowerPC (64-bit hard-float)
3.1.13. S/390 (32-bit)
3.1.14. S/390 (64-bit)
3.1.16. SPARC (32-bit)
3.1.17. SPARC (64-bit)
3.1.20. x86 (32-bit, Linux)
3.1.21. x86_64 (64-bit, Linux)
3.1.22. x86_64 (x32, Linux)
3.1.23. x86 (32-bit, Hurd)
3.2. Packaging Changes
Describe any distribution packing changes that may be required.