Convert scopeless BlockStmt to scoped to fix several --baseline regressions to pass
The change to ForLoop exposed an issue with some cryptic code that quietly drops the last statement in a Zip4 block.  We're not sure why this was done, prior to 2008, but it does not seem to be appropriate today
Update FORK counts for alloc with cyclic due to coerce wrapper change.

Vass's change to remove coercion wrappers (pull request #250) reduced
the comm FORK counts for this test as it did for others, but we didn't
notice that because this test had previously regressed.  Earlier today
I fixed that regression in pull #700, and now I'm fixing the cyclic
.good file for the reduced FORK counts.
Different approach to the mallocOutOfMemory problem: limit the heap size

Also made the test have a set end to its loop as Brad suggested instead of
letting it run to infinity when things don't work right.
Added a future for crash when creating privatized array/domain slices concurrently.
Added a test temp file to .gitignore.
Merge pull request #706 from vasslitvinov/add-future-test-hpl+replicated

Added a future for crash when creating slices of privatized array/domain concurrently.

From .future:

This test crashes intermittently at runtime in the forall loop with -nl4.

The errors I observed in various runs include:
* ReplicatedDist.chpl:272: error: attempt to dereference nil
* Caught a fatal signal: SIGABRT(6) on node 0/4
* *** glibc detected *** hplx_real: corrupted double-linked list: ....
* malloc.c:3091: sYSMALLOc: Assertion `.....' failed.

Uncommenting the commented-out code in the test and/or increasing 'fac'
should increase the probability of failure.

Valgrind detects "Invalid read of size 8", perhaps reliably,
even under -nl2.
In my setup (with fifo) it runs longer than several minutes,
I don't know if it ever terminates.

When this test is fixed, please enable this test for ReplicatedDist
by removing its .skipif:

  test/distributions/robust/arithmetic/kernels/hpl.chpl
Merge pull request #705 from lydia-duncan/fixOutOfMemory

Different approach to the mallocOutOfMemory problem: limit the heap size

Also made the test have a set end to its loop as Brad suggested instead of
letting it run to infinity when things don't work right.
Merge pull request #707 from noakesmichael/loopScoped

Convert For/While loop statements to be wrapped in a scoped BlockStmt

1) Update the build routines for ForLoop, WhileDoStmt, and DoWhileStmt to
make the outermost BlockStmt be scoped rather than scopeless.  This addresses
a regression for --baseline.

2) This change exposed a long standing curiosity with buildZip4 in AST/iterators.cpp.
That code had test that would cause the function to drop the last statement from the
body of the zip4 function.  This has been true for years and it's not clear why.  In
practice this is usually dropping a call to autoDestroy but every once in a while it's
dropping a "real operation".  Some aspect of the first commit caused a particular
move to be dropped that surfaced as 2 regressions.

Including the final statement "makes sense" and does not appear to introduce any new
regressions.

Compiled STD darwin/clang, STD linux/gcc, LLVM linux/gcc
Tested: full paratest   std --verify  std --baseline --inline
Reviewed: Discussed at length with Elliot
Converting fat TABs to 2-space TABs
Made a few simple changes that sped this up significantly

* Converted a range into a domain to avoid creating anonymous domains
  all the time.

* Improved the triangular iteration pattern to avoid zippered
  iteration, use a ref var, and avoid array slicing.
Change writeln()s of format()ed strings to writef()s

This was written before we had writef() in the library, so it
used a number of format() conversions which are pretty ugly
and heavyweight.  Changing to writef() for simplicity and
clarity.
Merge pull request #708 from bradcray/lulesh-regressions-week

Change writeln()s of format()ed strings to writef()s in LULESH

[trivial, not reviewed]

Lulesh was written before we had writef() in the library, so it
used a number of format() conversions which are pretty ugly
and heavyweight. Changing to writef() for simplicity and
clarity.

I was having trouble debugging an issue in LULESH which
motivated this change.
Convert fat TABs to 2-space TABs
Reformatting nbody variations

Reducing indentations to 2-space-based.
Removing TABs from some declarations of the bodies
Removing blank lines from others
Applying similar formatting to this as the others

SOmehow I missed it on the first pass.
Further edits to nbody tests

* changed 'do {' to simply '{'

* propagated fixes that I made to nbody_iterator_7.chpl to the
  others that are timing out in memleaks testing.
Merge pull request #709 from bradcray/nbody-regressions-week

Nbody speed improvements

[trivial, not reviewed]

Several of Albert's nbody variations have been timing
out on memleaks testing since being moved to a
(slower?) virtual machine.  This gives a good excuse
to speed up some of the slower ones that remain
interesting.

The meat of the changes included:

* pulling out some zippered iterators (which have
  proven slower than ideal in other cases) and
  replaced them with domain/range iterations
  and random access

* avoided the use of array slicing in the inner loop

* used 'refvar' declarations to capture references
  to the bodies in question instead of the previous
  two idioms.

This seems to reduce execution time by about 50%.

While here, I also did some cleanup:

* For all the tests, I reformatted them to not use such
  crazy wide indentation in favor of 2-space indentation.

* While here, I also made 'do {' idioms into simply '{'

* Also did a bit of reformatting of the bodies: removed
  TAB characters and got rid of some needlessly blank
   lines.
Skipping miminal modules tests for memleaks testing

I hadn't had the chance to diagnose this before, but
when running memleaks testing, we refer to configs
that are not present in minimal modules mode, so it
doesn't make sense to run these tests in that mode.
Merge pull request #710 from bradcray/minMod-regressions-week

Skipping miminal modules tests for memleaks testing

I hadn't had the chance to diagnose this before, but
when running memleaks testing, we refer to configs
that are not present in minimal modules mode, so it
doesn't make sense to run these tests in that mode.