This is consistent with my findings w/ XLC (mostly on BG/L and BG/P
front end nodes).
None of the 7.0, 8.0, 9.0 or 11.1 versions of XLC I tested could
generate correct atomics.
They either failed at build time, or failed the tests in test/asm/.
-Paul
On 2/23/2012 8:17 PM, Christopher Samuel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/02/12 15:12, Christopher Samuel wrote:
> I suspect this is irrelevant, but I got a build failure trying to
> compile it on our BG/P front end node (login node) with the IBM XL
> compilers.
Oops, forgot how I built it..
export
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/02/12 00:17, Jeffrey Squyres wrote:
> Please test!
I suspect this is irrelevant, but I got a build failure trying to
compile it on our BG/P front end node (login node) with the IBM XL
compilers.
make[5]: Entering directory
OpenPBS, PBS Pro, and Torque are all identical from our perspective - the
launcher code is the same.
On Feb 23, 2012, at 8:41 PM, Christopher Samuel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 23/02/12 09:44, Jeffrey Squyres wrote:
>
>> - PBS Pro, Open PBS, Torque
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/02/12 09:44, Jeffrey Squyres wrote:
> - PBS Pro, Open PBS, Torque
Does anyone actually use OpenPBS any more these days? It was abandoned
almost 11 years ago now from what I see (2.3.16 was June 2001).
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.3.3a1r4340
Start time: Thu Feb 23 21:07:00 EST 2012
End time: Thu Feb 23 21:09:57 EST 2012
Your friendly daemon,
Cyrador
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.4.1rc2r4342
Start time: Thu Feb 23 21:04:12 EST 2012
End time: Thu Feb 23 21:07:00 EST 2012
Your friendly daemon,
Cyrador
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.5a1r4341
Start time: Thu Feb 23 21:01:01 EST 2012
End time: Thu Feb 23 21:04:12 EST 2012
Your friendly daemon,
Cyrador
I'm not yet using the Mac OS X LLVM compilers. I have been under the
impression that LLVM compilers are not GNU compilers. However, given
the names llvm-gcc-x.x, I guess they are some sort of hybrid. (gcc
front end, LLVM backend?) I agree with Jeff's point about not getting
too
Sure, let's ship it in the tarball.
On Feb 23, 2012, at 1:28 PM, Brice Goglin wrote:
> Hello,
>
> "make check" doesn't report any single memory leak under valgrind
> anymore in trunk... except those from external libs such as libpci and
> libxml. I created the attached suppressions file to hide
Hello,
"make check" doesn't report any single memory leak under valgrind
anymore in trunk... except those from external libs such as libpci and
libxml. I created the attached suppressions file to hide them when
valgrind'ing hwloc programs. Just pass --suppressions=hwloc.supp to
valgrind.
For the
Sorry folks. That was intended just for Jeff's eyes, but my fingers
moved faster than my brain.
No offense was intended.
-Paul
On 2/23/2012 10:01 AM, Paul H. Hargrove wrote:
I think the VT folks get blamed often enough for build issues w/o
attributing one more problem to them.
On
I think the VT folks get blamed often enough for build issues w/o
attributing one more problem to them.
On 2/23/2012 9:47 AM, Jeffrey Squyres wrote:
Cool; thanks for setting this straight.
--
Paul H. Hargrove phhargr...@lbl.gov
Future Technologies Group
HPC
Cool; thanks for setting this straight.
Doesn't change the outcome, though -- I updated the README (i.e., something
like "update your Solaris Studio install!"). We have similar statements about
other broken/buggy compilers.
On Feb 23, 2012, at 12:45 PM, Paul H. Hargrove wrote:
> Just a
Just a Minor correction. Instead of:
- The C++ part of the build (VT) is deep within the OMPI build; it works
fine with the C compiler all the way up until that point
The correct facts are:
- The C++ part of the VT build requires CXXFLAGS=-library=stlport4 when
using the SS12 compilers.
-
Terry and I talked about this on the phone. Supporting facts (some of these
are repeated from Paul's prior posts):
- This happens with the C++ SS 12.2 compiler on supported Linux platforms
- The C++ part of the build (VT) is deep within the OMPI build; it works fine
with the C compiler all the
We finally have 1.5.5rc2:
http://www.open-mpi.org/software/ompi/v1.5/
Given the amount of testing we've had, this rc might actually be pretty close.
Lots and lots of changes since rc1; I'm not even going to bother to list them
all.
Please test!
--
Jeff Squyres
jsquy...@cisco.com
For
I don't think I want to get specific about the gcc versions on any platform,
unless we know that they *don't* work. There's too many versions and variants
of gcc out there to have an inclusive list -- I'd rather have an *exclusive*
list.
On Feb 23, 2012, at 3:39 AM, Paul Hargrove wrote:
>
On Feb 23, 2012, at 6:05 AM, TERRY DONTJE wrote:
> I actually think the systems tested line for Solaris should read:
> - Oracle Solaris 10 and 11, 32 and 64 bit (SPARC, i386, x86_64), with
> Oracle Solaris Studio 12.2 and 12.3
Done.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal
On 2/22/2012 8:53 PM, Jeffrey Squyres wrote:
Terry / Eugene --
Can you comment?
Sorry I cannot.
--td
On Feb 22, 2012, at 3:16 PM, Paul H. Hargrove wrote:
I think I have the beginning of a fix for this issue.
I had not even noticed earlier that the error in event.h is from the C++
I actually think the systems tested line for Solaris should read:
- Oracle Solaris 10 and 11, 32 and 64 bit (SPARC, i386, x86_64), with
Oracle Solaris Studio 12.2 and 12.3
--td
On 2/22/2012 8:55 PM, Paul H. Hargrove wrote:
Folks at Oracle should decide, but I suspect "Solaris 10" should be
And here is the 10.7 machine as promised:
ProductName: Mac OS X
ProductVersion: 10.7.3
BuildVersion: 11D50b
lrwxr-xr-x 1 root wheel 12 Oct 27 14:01 /usr/bin/gcc -> llvm-gcc-4.2
-Paul
On Wed, Feb 22, 2012 at 7:44 PM, Paul H. Hargrove wrote:
> I can get exact info from my
22 matches
Mail list logo