Update the cygwin entry slightly
Add a check to ensure that all PRIM_YIELD primitives are removed from the tree after lowerIterators.
Add a new future to quiet recordBug/test_likepy.

Investigation of this bug shows that recursive iterator inlining is not being done
completely.  It should include translation of PRIM_YIELD primitives, and does not.
Merge branch 'master' into triage
Note another instance of the waynew/example2 intermittent failure.
Workaround for translation bug that allows PRIM_YIELD to reach codegen.

Added the new function removeUncalledIterators() and a call to it at the end of
lowerIterators().  The new function looks for PRIM_YIELD calls that remain in the tree and
removes the functions that contain them.  The operative assertion is the if these
functions *had* been inlined by expandIteratorInline(), then the yields they contain would
have been replaced.

The correctness of this approach also relies on the more subtle assertion that the "dirty"
functions are not called directly.  In my investigation, I only saw the error case come up
when for loops were expanded within the body of _coforall_fn() helpers.  If such a
function contains a yield, it is expected that it will be called in the context of a for
loop, and will therefore be inlined.

Revised some comments, based on my improved understanding of what expandIteratorInline()
is doing.

While there, I cleaned up the interface to expandBodyForIteratorInline() by pushing the
collection of asts inside that function.  Since the function is called recursively, this
makes it clearer that the asts being traversed within eah invocation are merely the body
of the passed in iterator block (ibody).
Remove REGRESSIONS entries for memory/shannon/printFinalMemStat

The regressions file had noted that Michael's cache commit increased memory
usage by 8 bytes on July 11th for no-local and numa, leaving the test failing.
On August 4th, the no-local entry became no longer relevant because Tom's fix
to replicateGlobalWrappedRecordVars() improved memory usage by 64 bytes and
Tom updated the no-local.good file to reflect this.  Numa testing also improved
by this amount, but that was not noticed at the time.  The numa .good file has
now been altered to pass testing, so this entry will not be observed again
except by chance.  Though it is important to note that these changes occurred,
I do not feel it is useful to leave them in the REGRESSIONS file to be cleaned
up when the explanation is no longer known.
Update test_likepy.bad, due to added check_afterLowerIterators().
Add/update entry for parallel/begin/deitz/test_string_cat

This may be related to the tcmalloc change.
Add entry for knucleotide-chaining non-det seg faults

This may also be related to tcmalloc
Note the current tcmalloc issue, rearrange some of the failing test cases so
that they appear closer to my best guess at their source (tcmalloc).
Bump call stacks parallel/cobegin/deitz/test_big_recursive_cobegin

Made call stack size too low yesterday
Merge pull request #403 from ronawho/qthreads-testing

Bump call stacks parallel/cobegin/deitz/test_big_recursive_cobegin

[trivial, not reviewed]

Made call stack size too low yesterday
Move declaration for flattenNestedFunctions into passes.h.
Merge branch 'quietTestLikepy' of github.com:hildeth/chapel into quietTestLikepy
Adding the directory test/optimizations/cache-remote/ferguson/correctness to
the list of tests potentially affected by tcmalloc.  This case is different
because it is in fifo as opposed to qthreads, but the problem seems to be linked
to tcmalloc - it turned up first on the day tcmalloc went in and was not visible
on the day it was no longer present.
Remove Tom's passing futures, as they are no longer futures.
Do not copy qthreads mailing list with test results.

Now that qthreads is the default, it does not make sense to copy that list.
Merge pull request #404 from thomasvandoren/rm-qthreads-mailing-list

Do not copy qthreads mailing list with test results.

Now that qthreads is the default, it does not make sense to copy that list.
Add note that associative/bharshbarg/domains/opEquals was broken by const-ness
checking.