EdgyToolchainRoadmap

Differences between revisions 1 and 5 (spanning 4 versions)
⇤ ← Revision 1 as of 2006-06-09 12:55:47 →
Size: 764
Editor: dslb-088-073-106-124
Comment: add page
← Revision 5 as of 2006-06-23 09:24:21 → ⇥
Size: 2306
Editor: ALagny-109-1-2-101
Comment: multiarch additions
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * '''Contributors''': MatthiasKlose  * '''Contributors''': MatthiasKlose, JeffBailey
Line 10: Line 10:
 Desribe our plans with the toolchain

 * Versions targeted (mostly fixed, need to decide about Java 4.1/4.2)
 * Multiarch integration?		  * Versions targeted.
 * Multiarch integration / biarch updates
Line 17: Line 15:
Separate specs are GccSsp and JavaRoadmap.
Line 19: Line 19:
== Use cases ==

== Scope ==

== Design ==		 Edgy has a short release cycle, use edgy as a testbed for one major change, but keep the rest of the toolchain rather un-edgy and use the time to prepare a solid work for edgy+1 (EdgyPlusOneToolchainRoadmap).
Line 27: Line 23:
=== Code ===  * NPTL is enabled and the default in glibc-2.4, linuxthreads not enabled anymore
   * all release architectures and ia64 supported
   * hppa certainly broken
Line 29: Line 27:
=== Data preservation and migration ===  * details can be found in GccSsp
   * turn on -fstack-protector and see what happens (pending approval in GccSsp).
   * prepare a more solid solution for edgy+1
   * provide some kind of documentation / tutorial; not much included upstream
   * Add libssp0-dev as a dependency of gcc-4.1, or merge it into gcc-4.1.

 * multiarch/biarch related changes
   * no multiarch changes explicitely targeted for edgy, see if glibc, gcc, binutils can be changed to transparently install in multiarch locations.
   * biarch -m32/-m64 changes (See as well outstanding issues / discussion below)
     * on sparc, build a sparc64-linux-gnu compiler defaulting to sparc-linux-gnu by default (requested by the sparc port).
     * for i386, build a non-biarch compiler, plus a i386->amd64 cross compiler, which still can be called using gcc -m64.
   * provide <triplet>-<tool> wrappers for the biarch compilers.

 * Demoting compilers to universe, which are not necessarily needed for main (See outstanding issues).

 * upstream tools
   * glibc-2.4, in edgy.
   * binutils-2.17, needs testing and packaging, not yet available in unstable.
   * gcc-4.1.1, gcc-4.1.2 likely after edgy freeze; follow the 4.1 branch to some point, then apply patches for wrong-code/ice-on-valid failures.

Summary

  • Versions targeted.
  • Multiarch integration / biarch updates
  • Defaults for Stack Protection
  • Drop obsolete compiler packages

Separate specs are GccSsp and JavaRoadmap.

Rationale

Edgy has a short release cycle, use edgy as a testbed for one major change, but keep the rest of the toolchain rather un-edgy and use the time to prepare a solid work for edgy+1 (EdgyPlusOneToolchainRoadmap).

Implementation

  • NPTL is enabled and the default in glibc-2.4, linuxthreads not enabled anymore
    • all release architectures and ia64 supported
    • hppa certainly broken

  • details can be found in GccSsp

    • turn on -fstack-protector and see what happens (pending approval in GccSsp).

    • prepare a more solid solution for edgy+1
    • provide some kind of documentation / tutorial; not much included upstream
    • Add libssp0-dev as a dependency of gcc-4.1, or merge it into gcc-4.1.
  • multiarch/biarch related changes
    • no multiarch changes explicitely targeted for edgy, see if glibc, gcc, binutils can be changed to transparently install in multiarch locations.
    • biarch -m32/-m64 changes (See as well outstanding issues / discussion below)
      • on sparc, build a sparc64-linux-gnu compiler defaulting to sparc-linux-gnu by default (requested by the sparc port).

      • for i386, build a non-biarch compiler, plus a i386->amd64 cross compiler, which still can be called using gcc -m64.

    • provide <triplet>-<tool> wrappers for the biarch compilers.

  • Demoting compilers to universe, which are not necessarily needed for main (See outstanding issues).
  • upstream tools
    • glibc-2.4, in edgy.
    • binutils-2.17, needs testing and packaging, not yet available in unstable.
    • gcc-4.1.1, gcc-4.1.2 likely after edgy freeze; follow the 4.1 branch to some point, then apply patches for wrong-code/ice-on-valid failures.

Outstanding issues

BoF agenda and discussion

CategorySpec

EdgyToolchainRoadmap (last edited 2008-08-06 16:38:55 by localhost)