Update the cygwin entry slightly
Merge branch 'master' into triage
Note another instance of the waynew/example2 intermittent failure.
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.
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).
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.
Add note that associative/bharshbarg/domains/opEquals was broken by const-ness
checking.
Add note on the breakage of spec/Functions/variable-functions, for posterity.
Since the test is no longer relevant, the commit can be reverted.  Whee.

This reverts commit ea2c6c18d28c9fc5aa7b862c640c9fafde4e5f30.
Use "C for loop" in DefaultRectangular and remove posStrideIter

Default rectangular used to use a while loop in an iterator instead of
forwarding to ChapelRange as an optimization to avoid using a general strided
range iterator. With C for loops V2 this was changed to call into an optimized
range iterator for positively strided ranges. However, we noticed that for tests
like n-body we had a performance hit because of this.

The reason for this is because forwarding to ChapelRange introduces the
overhead of range construction. The posStridedIter also used alignedLow/High
which meant calls to chpl_diffMod.

In order to avoid these additional (and in the case of defaultrectangular
unnecessary) calls we are using a C for loop in DefaultRectangular. This is a
little unfortunate as we originally only wanted C for loops in ChapelRange, but
we don't envision needing them anywhere else. Since posStridedIter was only
around for DefaultRectangular, I'm removing that as well.
Add note to TRIAGE file on breakage of types/tuple/sungeun/iteration/forall
Add a prediff file to squash C error message line numbers.
The test failure has been resolved on all but the most lagging of testing
environments, so I am removing it from the TRIAGE file again.

This reverts commit 1983c430250c0e43925bfb0216b6c6090c5fab13.
Add a note for the test associative/bharshbarg/arrays/arraySetOps which was
failing non-deterministically.  Ben has since pushed a change to fix this, but
not all testing has come in and because it was failing non-deterministically,
it should be observed for a couple more days before victory is declared.
Note Elliot's resolution of the maximal range bugs.  Also added a date stamp
to the error Ben resolved so we can potentially remove it sooner.
Note the test failure of execflags/gbt/getenv under gasnet
Note failure of functions/diten/refArgIter in baseline testing