On May 19, 2009, at 1:22 PM, Joshua Bernstein wrote:
>
http://www.open-mpi.org/faq/?category=building#pathscale-broken-with-mpi-c++-api
They've been very responsive for me and their suggestions do
generally do the
trick. There is no doubt the compiler is smoking fast, its just about
compati
Jeff Squyres wrote:
Hah; this is probably at least tangentially related to
http://www.open-mpi.org/faq/?category=building#pathscale-broken-with-mpi-c++-api
This looks related, perhaps something about suggesting using the -gnu4 option
might be nice to add, if not there then maybe somep
Hah; this is probably at least tangentially related to
http://www.open-mpi.org/faq/?category=building#pathscale-broken-with-mpi-c++-api
I'll be kind and say that Pathscale has been "unwilling to help on
these kinds of issues" with me in the past as well. :-)
It's not entirely clear fro
Well,
I spoke Gautam Chakrabarti at Pathscale. It seems the long and short of it is
that using OpenMP with C++ with a GNU3.3 (RHEL4) frontend creates some
limitations inside of pathCC. On a RHEL4 system, the compilier activates the
proper frontend for GCC 3.3, this is what creates the crash.
FWIW, I'm able to duplicate the error. Looks definitely like
a[nother] pathscale bug to me.
Perhaps David's suggestions to disable some of the optimizations may
help; otherwise, you can disable that entire chunk of code with the
following:
--enable-contrib-no-build=vt
(as Ralph menti
Pathscale supports -O3 (at least as of the 3.1 line). Here are some
suggestions from the 3.2 Users Manual you may also want to try.
-david
If there are numerical problems with -O3 -OPT:Ofast, then try either of the
following:
-O3 -OPT:Ofast:ro=1
-O3 -OPT:Ofast:div_split=OFF
Note that ro
Last I checked when we were building here, I'm not sure Pathscale
supports -O3. IIRC, O2 is the max supported value, though it has been
awhile since I played with it.
Have you checked the man page for it?
It could also be something in the VampirTrace code since that is where
you are failin
On Thu, 2009-05-14 at 13:35 -0700, Joshua Bernstein wrote:
> Greetings All,
>
> I'm trying to build OpenMPI 1.3.2 with the Pathscale compiler, version
> 3.2. A
> bit of the way through the build the compiler dies with what it things is a
> bad
> optimization. Has anybody else seen this,
Greetings All,
I'm trying to build OpenMPI 1.3.2 with the Pathscale compiler, version 3.2. A
bit of the way through the build the compiler dies with what it things is a bad
optimization. Has anybody else seen this, or know a work around for it? I'm
going to take it up with Pathscale of course
