charm AT lists.cs.illinois.edu

Subject: Charm++ parallel programming system

List archive

[charm] Release candidate for Charm++ 6.7.0

From: Nikhil Jain <nikhil AT illinois.edu>
To: PPL <ppl AT cs.illinois.edu>, "namd-ppl AT cs.illinois.edu" <namd-ppl AT cs.illinois.edu>, "openatom-ppl AT lists.illinois.edu" <openatom-ppl AT lists.illinois.edu>, "cosmology-ppl AT cs.uiuc.edu" <cosmology-ppl AT cs.uiuc.edu>, Jae-Seung Yeom <jyeom AT vbi.vt.edu>, kbisset AT vbi.vt.edu, Charm Mailing List <charm AT cs.illinois.edu>
Subject: [charm] Release candidate for Charm++ 6.7.0
Date: Tue, 10 Nov 2015 21:16:26 -0600

Hello Everyone,

I've just tagged a release candidate for the next stable release, version 6.7.0, of Charm++. The git tag is v6.7.0-rc1. It has passed all of the usual testing in autobuild, except the following two issues that we are still looking into:

- #838 Thread migration crashes on all darwin builds

- #860 CUDA threads not killed at end of program in multicore builds

It would be good to get affirmative test results from the primary application teams on the platforms and configurations people use in practice. Could someone from the following teams confirm, by *explicitly responding to me only*, that all is well with the tag v6.7.0-rc1

- NAMD

- ChaNGa

- OpenAtom

- EpiSimdemics
- XPACC

- JetAlloc

Here is a concise list of changes that are slated for 6.7.0 (excluding the numerous bug fixes):

1) New API for efficient formula-based distributed spare array creation.

2) CkLoop is now built by default.

3) CommLib has been deleted.

4) PXSHM auto detects the node size. +nodesize is deprecated.

5) Out-of-tree build is now supported.

6) New target: multicore-linux-arm7

7) CmiBool has been dropped in favor of C++'s bool.

8) CBase_Foo::pup need not be called from Foo::pup.

Thanks

On behalf of PPL,

Nikhil

Nikhil Jain, nikhil.jain AT acm.org, http://charm.cs.uiuc.edu/people/nikhil
Doctoral Candidate @ CS, UIUC

[charm] Release candidate for Charm++ 6.7.0, Nikhil Jain, 11/10/2015