[Bug target/9511] [Cygwin] Can't detect whether threading enabled

[rwgk at yahoo dot com]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9511



------- Additional Comments From rwgk at yahoo dot com  2003-06-22 11:46 -------
David asked me to comment.

I've tried gcc 3.3 only under Redhat 8.0 and Mac OS X.

IIRC there is one bug that lead to code rearrangement in Boost.Python.
The problem is (e.g.) reported here:

http://mail.python.org/pipermail/c++-sig/2003-May/003935.html

Here is our final workaround (not marked as such in the code):

http://cvs.sourceforge.net/cgi-
bin/viewcvs.cgi/boost/boost/boost/python/converter/as_to_python_function.hpp.dif
f?r1=1.1&r2=1.2

Under Redhat 8.0 the only other problem I know about is that the
optimizer is broken for *some* of our extensions, but I've not tried to
track this down.

Under Mac OS 10 the worst problem are the internal compiler errors,
as reported here:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10922

There is also a problem with the Boost alignment calculation under OS
10, but I don't think (any longer) that this is a gcc 3.3 bug. For the
records, here is a related thread:

http://aspn.activestate.com/ASPN/Mail/Message/1641891

Under Mac OS 10 the gcc 3.3 optimizer is broken for *almost all* of
our extensions. You can reproduce this by following the instructions
given here:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10922#c5

Hope this is useful even though it is not strictly related to
the 9511 bug report.

Ralf