Add dataPar related values to default these() iterators

[reviewed by David and Lydia]

This patch adds data parallelism arguments to the default array and
domain iterators with default values set to the appropriate config
consts (i.e., dataParTasksPerLocale, dataParIgnoreRunningTasks,
dataParMinGranularity).  This enables forwarding from other iterators
that may want to use different values, e.g. BlockDom.

Other changes:

- Explicitly pass all arguments to _computeBlock() even though the
  standalone default versions can use the default values of 0.  This
  did not appear to affect performance.

- Move the definition of the dataPar configs into DefaultRectangular
  to enable the serial these() iterator to refer to them when
  initializing other modules.  This is needed by the serial iterator
  only because the signatures of all the iterators need to match if
  you want to be able to use the iterator directly in a loop (rather
  than forwarding through another iterator).

- Fixed a type-o in a comment



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22519 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Add a few test programs that exercise iterator forwarding, including the default these() iterators.



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22520 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Update to reflect the current state of our GASNet.

[Not reviewed.]

We switched to GASNet 1.22.0 with r22160 (2013-10-22).  Following that,
in r22511 (2014-01-07) we installed a small configure.in change from the
GASNet team to correct a problem seen at initialization time when using
the Cray-specific Aries substrate.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22521 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove GASNet 1.20.2.

[Not reviewed.]

We've been using 1.22.0 by default in regular testing since 10/22/13,
and also have just confirmed that it works as well as (better than,
actually) 1.20.2 on Cray XE and XC30 systems, so 1.20.2 can go.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22522 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Don't run single-thread fifo tests with --no-local, because they always fail.

[Not reviewed.]

This is a follow-up to r22492.  Don't run QueuedTasks, OneThread, and
OneThreadSyncStmt when they are compiled with --no-local, because they
hang in that configuration just as they do with CHPL_COMM!=none.

(These are still perfectly valid tests, because they actually test our
tasking behavior, not anything to do with our multilocale behavior.)


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22523 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Third time's the charm: when start_test was auto-generating spec tests, it was
using different locations for creating the .tmp files and looking for the .tmp
files it created.  I unified their location - I'm not certain why this ever
worked before.  Performance testing should work again now.



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22524 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
I noticed that the comment at the top of start_test detailing the command-line
options was out of date, so I updated it to reflect the output given by running
start_test -h



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22525 3a8e244f-b0f2-452b-bcba-4c88e055c3ca