This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Fri, May 24, 2013 at 05:09:34PM +0200, Rainer Orth wrote: > Jakub Jelinek <jakub@redhat.com> writes: > > > So, adjusted patches attached, ok for trunk/4.8 if they pass > > bootstrap/regtest? Guess Rainer will need to on top of that adjust > > Solaris baseline_symbols.txt files. > > I meant to look into that, but usually I only update the baselines for > x.y.0 releases, not micro releases. The addition of GLIBCXX_3.4.19 > might justify an exception, though. Well, I've hand edited the Linux baseline_symbols.txt rather than really regenerating (can't bootstrap/regtest that quickly on all arches), but I see no reason why Solaris can't be done the same way. If I understand it right, Solaris doesn't allow foo@VER_1 together with foo@@VER_2, thus the attached updated patch should contain what I expect on Solaris, thus just regtest of that should reveal if the assumption is right. Ok, 4.8 x86_64/i686-linux bootstraps running now, will do trunk ones next, and simultaneously with that ppc/ppc64/s390/s390x/arm-linux. Jakub
Attachment:
49
Description: Text document
Attachment:
48
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |