Upcoming 1.10 Release

11 views
Skip to first unread message

Dylan

unread,
Sep 3, 2013, 3:47:50 PM9/3/13
to qthr...@googlegroups.com
Hi,

We are planning to push out a 1.10 release ahead of SC 13. Any concern, suggestions, or objections? In particular, if you have any outstanding commits you would like to get in, please contact me so that we can plan the release accordingly.

Dylan Stark
Scalable System Architectures Dept.
Sandia National Laboratories

Brad Chamberlain

unread,
Sep 3, 2013, 4:55:28 PM9/3/13
to qthr...@googlegroups.com, Greg Titus, Michael P. Ferguson

Hi Dylan --

[Cc:ing Greg and Michael who were involved in a number of these mods]

I'm attaching a patch that contains all local mods we've done against
qthreads-1.9 (qthreads-changes-chpl.patch), as well as the commit messages
that describe the changes (SVNLOG). These commits fall into a few
different categories, that I didn't tease apart as well as I perhaps
could:

* stack overflow capabilities -- I believe that these are redundant with
commits you've already made on your tree, but which we brought over
early. r21328 and r21329

* Michael Ferguson's changes to get qthreads and RE2 playing well
together. I believe that he's sent these changes to qthread.h to you
previously as well -- at least, he says so (r21375).

* All the others relate to changes to the tasking interface related to
hierarchical locales and aren't worth committing piecemeal -- they're
not always monotonic in getting from 1.9 to where we are today.

I think the changes in category 1 and 2 mostly touch a small subset of
files that are independent of Chapel; so based on the assumption that you
should already have those mods, I'm sending a second patch
(qthreads-changes-chpl-edited.patch) that focuses on the stuff I'm more
certain you don't have and will need. My hypothesis is that this patch
should integrate fairly cleanly and give us everything we need to make
Qthreads 1.10 work with Chapel 1.8.

If you were able to accept these changes to qthreads trunk, I think that
would be ideal. I'd be interested in trying a release candidate before
you cut 1.10 if possible, to try and head off obvious issues. If for some
reason you wouldn't/couldn't accept the changes back, we could apply them
again to our snapshot of 1.10.

As mentioned in my previous mail, I think the right thing to do (after the
release at this point) is to move the Chapel-Qthreads interfaces over to
the Chapel source tree since we seem to be banging on them harder than you
guys these days. We'll have to make sure that's OK with the laywers on
both sides, though I think we're evolving toward a world where that
shouldn't be an issue.

Let me know if you have any troubles/questions with these patches,
-Brad
> --
> You received this message because you are subscribed to the Google Groups "qthreads" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to qthreads+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
qthreads-changes-chpl.patch
SVNLOG
qthreads-changes-chpl-edited.patch

Stark, Dylan

unread,
Sep 4, 2013, 2:38:05 PM9/4/13
to qthr...@googlegroups.com, Greg Titus, Michael P. Ferguson
Brad,

Greg and Michael sent over the first two sets of patches already, so we
should be good with respect to those.


Thanks for putting together the last collection of commits. I will apply
those to the release branch and send you a tarball for testing.

Dylan
Reply all
Reply to author
Forward
0 new messages