Differences between revisions 13 and 14
Revision 13 as of 2015-01-13 19:38:37
Size: 6837
Editor: bd3dcf37
Revision 14 as of 2015-01-23 21:31:03
Size: 6905
Deletions are marked like this. Additions are marked like this.
Line 93: Line 93:
 * Fix semaphore destruction (BZ #12674) [[https://sourceware.org/ml/libc-alpha/2014-12/msg00155.html]]
 * powerpc64 optimized string implementations:
 * --(Fix semaphore destruction (BZ #12674) [[https://sourceware.org/ml/libc-alpha/2014-12/msg00155.html]])--
 * --(powerpc64 optimized string implementations:)--
Line 114: Line 114:
 * Intel vecotorized libm - libmvec
Line 143: Line 144:

==== NIOS2 ====


1. Current status

The release branch of glibc-2.21 is maintained by Carlos O'Donell and its current release is 2.21.0, which we expect to tag on January 30th 2015. 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?

  1. Is the fix committed in master? It has to be, unless it's not applicable to master (e.g. code has been rewritten meantime).
  2. Do you have commit permissions? If so, go ahead if you think it's reasonably safe. break;
  3. 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;
  4. Add the glibc_2.21 keyword to the appropriate bug report.
  5. 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!).

2. Planning

What things do we want to accomplish this release?

2.1. Release blockers?

2.2. Desirable this release?

2.3. Postpone to next release (2.22)

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 ?


3.1.1. Architecture-independent

3.1.2. AArch64

3.1.3. Alpha

3.1.4. ARM

3.1.5. HPPA

3.1.6. IA64

3.1.7. M68K

3.1.8. MicroBlaze

3.1.9. MIPS

3.1.10. NIOS2

3.1.11. PowerPC (32-bit soft-float)

3.1.12. PowerPC (32-bit hard-float)

3.1.13. PowerPC (64-bit hard-float)

3.1.14. S/390 (32-bit)

3.1.15. S/390 (64-bit)

3.1.16. SH

3.1.17. SPARC (32-bit)

3.1.18. SPARC (64-bit)

3.1.19. TILE-Gx

3.1.20. TILEPro

3.1.21. x86 (32-bit, Linux)

3.1.22. x86_64 (64-bit, Linux)

3.1.23. x86_64 (x32, Linux)

3.1.24. x86 (32-bit, Hurd)

3.2. Packaging Changes

Describe any distribution packing changes that may be required.

3.2.1. Minimum required gcc version increased to 4.6

The minimum GCC version that can be used to build this version of the GNU C Library is GCC 4.6. Older GCC versions, and non-GNU compilers, can still be used to compile programs using the GNU C Library.

3.2.2. -Werror is enabled by default

The -Werror compiler flag in now enabled by default when building glibc. Although most warnings when building have been addressed, you may need to pass "--disable-werror" to configure when building with a toolchain combination that was untested by the developers.

None: Release/2.21 (last edited 2015-12-28 17:27:02 by MikeFrysinger)