- Libgcc is currently built from inside the GCC subdirectory. The goal of this project is to create a top-level directory named libgcc, build it after the gcc subdirectory is finished, and compile no target code in the gcc directory. The first pass leaves most of the source files and configuration in the GCC directory, so most targets which build things in typical styles do not need to be updated. Over time, we can migrate code incrementally to the new libgcc directory. That is less disruptive.
- Daniel Jacobowitz
- Some contributions from others, e.g. Paolo Bonzini
- This project was gotten into a functional state on a branch in late 2005, but has not been updated; it needs a week's work in cleanup and testing on various platforms. I estimate it can be ready by 2006-11-01. I will test on several platforms, but the chances of breakage on other platforms are fairly high; accordingly I consider this a stage 1 project.
- Eventually, this will allow some build complexity to be removed, because every directory will be strictly build, host, or target. It will also simplify building the compiler without the runtime libraries, or the runtime libraries without the compiler - even someday picking the set of multilibs independently from the compiler build process.
- The new directory has to be created, and various information saved during the GCC build for later reuse by the libgcc build (a transitional measure).