If we don't install libgcc_s.10.[45].dylib, our gcc links binaries
with *both* /usr/lib/libgcc_s.1.dylib and
${GCC_PREFIX}/lib/libgcc_s.1.dylib, which is certainly a bad thing.
The problem was already reported to the upstream but it caught
seemingly no attention:
http://gcc.gnu.org/ml/gcc-help/2010-07/msg00164.html
This is the list of problem reports (PRs) from GCC's bug tracking
system that are known to be fixed in the 4.5.3 release. This list
might not be complete (that is, it is possible that some PRs that
have been fixed are not listed here):
http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.5.3
On the PowerPC compiler, the altivec builtin functions vec_ld and
vec_st have been modified to generate the Altivec memory instructions
LVX and STVX, even if the -mvsx option is used. In the initial GCC
4.5 release, these builtin functions were changed to generate VSX
memory reference instructions instead of Altivec memory instructions,
but there are differences between the two instructions. If the VSX
instruction set is available, you can now use the new builtin
functions vec_vsx_ld and vec_vsx_st which always generates the VSX
memory instructions.
Packaged by Marko Schütz, improved by Kai-Uwe Eckhardt.
This is the gcc 4.5 compiler suite.
This package has a test target. For testing (only), this
package requires devel/dejagnu and devel/autogen.
