Hardcode Solaris v2 mapfile syntax with Solaris ld
Simplifies Solaris linker mapfile handling by removing obsolete checks.
This commit hardcodes the use of Solaris v2 mapfile syntax for GCC’s Solaris linker (ld). Previously, GCC supported both v1 and v2 mapfile syntaxes, distinguished by configure-time checks. As Solaris 11.0 introduced v2 syntax, and only newer versions are now supported, these checks are no longer necessary. The change also prevents issues during non-bootstrap builds where the build compiler’s linker might differ from the stage1 compiler’s linker. Mapfiles are now unconditionally used if the built compiler employs Solaris ld.
In Details
Removes configure checks for Solaris ld's mapfile syntax (v1 vs v2) and unconditionally applies v2 syntax, as it has been the standard since Solaris 11.0. This simplifies configuration and avoids regressions in non-bootstrap builds where the build compiler's ld might be different from the stage1 compiler's ld. The clearcap.map and libgcc-unwind.map files now directly use v2 syntax, with obsolete v1 configuration removed.
- Mapfile
- A file used by linkers to specify how symbols should be placed in the output file, control sections, and other linking-related directives. Solaris ld uses a specific mapfile syntax.
- Solaris ld
- The linker utility provided by the Solaris operating system. It is responsible for combining object files and libraries into an executable or shared library.
- Bootstrap build
- A compiler build process where an older version of the compiler is used to compile a newer version. This is a common method for building compilers.