> Please post a simple example on the Python developer list that can > reproduce the error with GCC 4.4. We have had issue with new GCC > releases in the past. Sometimes new optimizations are the culprit of > strange faults. You may want to play around with different -O levels, > too. Sometimes the error doesn't occur with less optimizations. Please > make sure you are using the correct compiler flags, especially > -fno-strict-aliasing and -fwrapv. python2.6-config should give you the > correct compilers flags.
Yes, everything is compiled through python's dist utils, so I don't think I'm missing something that should be there. However, I'm no longer using some of the custom optimization flags, such as -ftree-parallelize-loops=N (and a couple of others), which require gomp to be linked into the program. Without those, the error goes away. Note that it affects both gcc 4.3 and 4.4, though I haven't tested it against 4.4.[234], just gcc 4.4.1. I'll get together a small example to post there; I have a pretty crazy academic deadline coming up on Monday, so I'll do it first thing after that. -- Hoyt ++++++++++++++++++++++++++++++++++++++++++++++++ + Hoyt Koepke + University of Washington Department of Statistics + http://www.stat.washington.edu/~hoytak/ + [email protected] ++++++++++++++++++++++++++++++++++++++++++ _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
