Hi Hoyt,
Thanks for the thorough description of getting everything to work.
On Sat, Mar 26, 2011 at 12:14 AM, Hoyt Koepke
hoy...@stat.washington.edu wrote:
Okay, even better news. After a little bit of probing around, it
turns out that some of the errors, namely the one in the interpolator,
Thanks for the thorough description of getting everything to work.
You're welcome. I'm glad people find it helpful :-).
-ipo -- okay for linker / c++, but not elsewhere. For C, it causes
the long_double_representation() function in setup_common() to fail
(I'll note this on the
Okay, so here's a follow up on my progress. Apologies in advance for
the long email here, but I'd like to be thorough about this before I
forget.
For the sake of completeness, here's my setup. I'm running python
2.7.1 compiled from source with icc. I'm running ubuntu 10.10 on one
of intel's
Okay, last update. I finally have got everything to work.
It turns out the problems that I had earlier with f2py were due to
intel's -ipo flag. So the only place this flag works is with the C++
code, not fortran or c.
Also, I forgot to mention -- the qhull_a.h method has a workaround for
some
On Fri, 25 Mar 2011 13:46:41 -0700, Hoyt Koepke wrote:
[clip]
Also, I could still not get the CloughTocher2DInterpolator to not
segfault.
Backtrace would be useful here. It's probably best to recompile with
-O0 and some debug flags enabled in the compiler to get something
reasonable out.
--
Okay, even better news. After a little bit of probing around, it
turns out that some of the errors, namely the one in the interpolator,
were due to intel's handling of floating point values at higher
optimization levels. Thus the two rather important flags, if you wish
to avoid
Hello,
I've been trying out intel's compiler with python and so far things
have been going pretty well. I managed to compile python 2.7.1 with
icc (with help from
http://software.intel.com/en-us/forums/showthread.php?t=56652), so
distutils automatically defaults to the icc compiler. So far a
