On Mon, 30 Aug 2010, Uros Bizjak wrote: > On Mon, Aug 30, 2010 at 7:53 PM, Uros Bizjak <ubiz...@gmail.com> wrote: > > >>> I'm not familiar in versioning stuff, but since soft-fp symbols are > >>> part of generic libgcc-std.ver for a long time (before 4.5.0), I > >>> believe, it is enough to patch only configure files (see i.e. commits > >>> that enabled soft-fp on mingw/cygwin/-gnu*). > >> > >> It will "work", but not properly. ?One should never have symbols > >> magically appear in old versions. ?If you add the symbols to the > >> proper current version number in a config/gcc/i386/libgcc-bsd.ver, > >> they'll appear at the right place. > > > > Can someone please help here? > > Attached is my best (untested) shot at libgcc-bsd.ver. Someone has to > write i386/t-freebsd (similar to i386/t-linux) and connect it to the > build system. The versioning assumes that this will be committed to > 4.5.x first.
I advise copying libgcc-sol2.ver, with GCC_4.5.0 changed to GCC_4.6.0, unless you have some reason for actually needing different sets of symbols, since the Solaris version has already been reviewed as including all relevant symbols. (Plus, as previously discussed, the appropriate %inherit and empty GCC_4.6.0 version in libgcc-std.ver - like those for GCC_4.1.0 which also only has symbols for some targets, for example.) The Windows versions didn't need to allow for symbol versioning since that target doesn't support it. The GNU/Linux versions got some symbol versions wrong initially so are not a good example to work from for other OSes. Thus I recommend the Solaris version as an example from after the bugs in this area had been worked out. -- Joseph S. Myers jos...@codesourcery.com
