Update chown/permission_error test to work, even when uid/gid is 1000.

Previously, this test assumed that calling chown 1000:1000 file.txt was
invalid. That turns out to be valid if the current uid/gid is 1000/1000.

Update the test to take uid/gid as config consts and then add one to both to
get invalid uid/gid value.
Apply patch from Brice Goglin.

Details are here:

  http://www.open-mpi.org/community/lists/hwloc-users/2014/11/1118.php
Annotate the nights where NPB EP and IS performed better, used -E

I had misinterpretted the desire to use -E as a desire to use it nightly rather
than a desire to maintain default behavior but compare it to tweaked behavior.
Since there isn't a good way to compare them (our execenvs don't allow multiple
settings), decided to just leave the default for now.
Send darwin regression mail to normal lists (for gasnet.darwin)

Previously it was only sent to the all regressions list. The non-deterministic
errors have been cleaned up so it makes sense to send it to the normal lists.

Same idea as 7ad1f14e2a6f5febba3a03754c3487b5be7869f4, but I missed this file
Introduce transitional CForLoop::loopHeaderSet(init, test, incr)
Convert a use of blockInfoSet on CForLoop in to the transitional assignment
Merge pull request #897 from lydia-duncan/annotateEOptionUse

Annotate the nights where NPB EP and IS performed better, used -E

I had misinterpretted the desire to use -E as a desire to use it nightly rather
than a desire to maintain default behavior but compare it to tweaked behavior.
Since there isn't a good way to compare them (our execenvs don't allow multiple
settings), we decided to just leave the default for now. Since that churn is
reflected in the nightly graphs, annotate it so we don't forget.

Note, the commit in question also affected FT, but for sizes we don't run nightly.
Move the blockTag assignment in to loopHeaderSet
Merge pull request #888 from thomasvandoren/robustify-chown-test

Update chown/permission_error test to work, even when uid/gid is 1000.

Previously, this test assumed that calling `chown 1000:1000 file.txt` was
invalid. That turns out to be valid if the current uid/gid is 1000/1000.

Update the test to take uid/gid as config consts and then add one to both to
get invalid uid/gid value.
Merge pull request #898 from ronawho/darwin-regression-mail

Send darwin regression mail to normal lists (for gasnet.darwin)

Previously it was only sent to the all regressions list. The non-deterministic
errors have been cleaned up so it makes sense to send it to the normal lists.

Same idea as 7ad1f14e2a6f5febba3a03754c3487b5be7869f4, but I missed this file
Merge pull request #899 from noakesmichael/lower-0

Provide a transitional API for CForLoop and utilize in lowerIterators

Compiled: STD clang/darwin, STD gcc/linux64, LLVM gcc/linux64
Tested: paratest --verify
Review: None
Save the problem sizes for RA and STREAM variants

We're observing some strange cyclic behavior for RA on one of our performance
test machines that seems related to when the machine gets rebooted.  Since RA
is known to compute some of its size based on memory, we figured that saving
the problem size information from night to night might show us more of the
picture (and if not, at least serve as a sanity check that it is running the
same every night).  STREAM was also not saving this information, so the same
change was made to it.

Implementation details: I decided to create separate .dat files to store this
information as adding information to track to a .dat file has necessitated
adding a column to it manually, the script will not update the columns
otherwise.  These values are sanity checks so I think it is better to clutter
up the directory rather than the information in the files themselves.
Merge pull request #900 from lydia-duncan/saveHPCCProbSizes

Save the problem sizes for RA and STREAM variants [ok'd by elliot]

We're observing some strange cyclic behavior for RA on one of our performance
test machines that seems related to when the machine gets rebooted. Since RA
is known to compute some of its size based on memory, we figured that saving
the problem size information from night to night might show us more of the
picture (and if not, at least serve as a sanity check that it is running the
same every night). STREAM was also not saving this information, so the same
change was made to it.

Implementation details: I decided to create separate .dat files to store this
information as adding information to track to a .dat file has necessitated
adding a column to it manually, the script will not update the columns
otherwise. These values are sanity checks so I think it is better to clutter
up the directory rather than the information in the files themselves.
Accept increased leak counts to quiet domainMaps tests.

The fix for early destruction of the contents of tuples #860 caused memory leaks to
increase (only) in memory/sungeun/refCount/domainMaps.

A previous attempt to quiet these tests #895, did not succeed.

This patch undoes #895 and instead updates the affected .good files to quiet the test.

The reasoning behind this approach is:
 - The results that are affected -- creating a domain and array in using replicated
   distribution -- seem specific to the implementation of Replicated Distributions in the
   affected configurations: gasnet and no-local.  (Interestingly, the numa configuration is
   unaffected.)
 - Since memory allocated for domains and arrays currently leaks in many configurations,
   more work is required in this area.  To facilitate progress in this area when it is
   undertaken, it is probably better to have the logic for autoCopy and autoDestroy be as
   simple as possible.
 - The case that was fixed for tuples in #860 was clearly wrong, whereas the previously
   lower leakage for the replicated distribution under gasnet and no-local may be
   considered fortuitous.
Preparation for BasicBlock changes
Print more timings in sub_test

sub_test currently prints the total time it took to execute which is really
useful information at times. sub_test can run over a whole directory and
sometimes you want finer grained timing so this adds timing stats on a per
test basis.

It prints:
 - the compilation time for each compile of the test
 - the execution time for each run of the test
 - the total time for all compilations, and executions of the test

I wanted to add execution time to look at total execution time for multi-locale
perf runs, but Thomas thought (and I agree) that timing compilation and total
test time is useful as well.
Merge pull request #889 from thomasvandoren/fix-hwloc-build-for-32bit

Fix hwloc build on 32bit platform with OPTIMIZE=1.

Previously, building hwloc with `OPTIMIZE=1` resulted in this failure:

```
... snip ... 
  CC topology-x86.lo 
/home/vagrant/src/hwloc/include/private/cpuid-x86.h: Assembler messages: 
/home/vagrant/src/hwloc/include/private/cpuid-x86.h:40: Error: symbol 
`Lhwloc1' is already defined 
Makefile:878: recipe for target 'topology-x86.lo' failed 
make[1]: *** [topology-x86.lo] Error 1 
make[1]: Leaving directory '/home/vagrant/src/hwloc/hwloc' 
Makefile:615: recipe for target 'all-recursive' failed 
make: *** [all-recursive] Error 1 
```

Brice Goglin fixed the issue with the changes applied in this pull request.

I applied the patch to the hwloc 1.9.1 in this repo. I also ran the full suite of tests
on linux32 to verify it did not introduce new issues. It did not.

More details here:

  http://www.open-mpi.org/community/lists/hwloc-users/2014/11/1118.php
Merge pull request #902 from ronawho/print-exec-time

Print more timings in sub_test

[reviewed by @thomasvandoren]

sub_test currently prints the total time it took to execute which is really
useful information at times. sub_test can run over a whole directory and
sometimes you want finer grained timing so this adds timing stats on a per
test basis.

It prints:
 - the compilation time for each compile of the test
 - the execution time for each run of the test
 - the total time for all compilations, and executions of the test

I wanted to add execution time to look at total execution time for multi-locale
perf runs, but Thomas thought (and I agree) that timing compilation and total
test time is useful as well.
Accepted increased leaks due to forall intents; added futures.
Merge pull request #904 from vasslitvinov/address-memleaks-in-numa-from-forall-intents

Accepted increased leaks due to forall intents; added futures.

* Accepted the additional memory leak of 16 bytes due to forall intents #614
in several tests exposed by "numa" testing, by adjusting .good files.

They are due to the same cause as in #614 for this test:

  memory/sungeun/refCount/domainMaps.chpl

For a detailed explanation, see the commit df8e3b0.

* Added two futures that expose this issue:
    memleaks1-minimal.chpl is the smallest amount of code that hits it;
    memleaks2-BlockDist.chpl is a realistic example.
  I added .skipifs to test these only in a couple of configurations.
  Once the leaks are fixed, .skipifs can be removed.

* While there:
 - created test/parallel/forall/
 - moved parallel/taskPar/forallIntents/*
   to test/parallel/forall/vass/