> > Unless one of the later flags is cancelling it out, or there's a > > compiler bug, we should be clean here.
> I did a build with CBE (/ws/onnv-tools/SUNWspro/SS11/bin/cc). The flag > is set on the compile command line, but %g2 is still being used. > > $ which cc > /ws/onnv-tools/SUNWspro/SS11/bin/cc > $ cc -V > cc: Sun C 5.8 Patch 121015-02 2006/03/29 > usage: cc [ options] files. Use 'cc -flags' for details > $ grep IntAtom" log/buildit-XW > ... > cc -c -xO3 -xbuiltin -xlibmil -Xc -xF -xarch=v8 -xregs=no%appl -mt > ... > $ dis xc/lib/X11/IntAtom.o | grep g2 > _XInternAtom+0x26c: 84 0a 60 03 and %o1, 0x3, %g2 That is, if I'd upgrade to a more recent nevada build than snv_48 (e.g. snv_60) the problem would still be there? Btw. another check for this problem is % dis /usr/openwin/lib/libX11.so.4 | grep %g2 ... [ lots of code using the %g2 register ] ... % I also have an old S10 6/2006 installation, and the same command produces *no* output for the S10 6/06 libX11.so % dis /sol10/usr/openwin/lib/libX11.so.4 | grep %g2 % All /usr/openwin/lib/lib*.so* shared libraries seem to be affected. This message posted from opensolaris.org
