Add an example of using the targetLocales method on arrays
Merge branch 'master' of github.com:chapel-lang/chapel into dist-primer-lsq
Adding exampels for the 'localSubdomain(s)' functions
Fix for io_test C compilation error.

The error message being displayed by the C compiler (GCC version 4.4.1 or newer) is
meaningful.  It warns that the program is attempting to free something that is not
heap-allocated -- in this case "\n" and the definitions of other ioLiterals.

The reason why the error only appears when --fast is supplied is that aggressive inlining
brings the call to free() into the function where an ioLiteral is passed to it, so under
those circumstances the C compiler can see that something stupid is being attempted.

In the original code, the author thought is was safe to free by explicitly avoiding known
cases where the contents of a c_string was owned by another program entity.  However,
since the IO module also supplies unowned c_strings it is unsafe in general to delete
them.  I added comments liberally to the module code where c_strings are accessed, so
future programmers are warned away from this practice.

Looking forward, except where performance is a concern, strings should be used in
preference to c_strings.  The new implementation of strings will manage memory correctly,
so the programmer who uses such objects need not concern himself with ownership details.
Merge branch 'master' into fixCStrings
Example for Cyclic; Example for 'localSubdomains' on Block
Add a primer for array vector operations

This primer walks through the new vector-like capabilities on 1D arrays.
Merge branch 'master' into fixCStrings
Work around lack of kernel scheduling affinity on KNC compute nodes.

The KNC compute nodes we have access to seem not to have kernel affinity
scheduling present.  Either that, or perhaps it's confused: we get masks
with no bits set returned from sched_getaffinity().  To work around this
for now, just don't apply the scheduling affinity limiting in the two
functions that return the number of physical and logical CPUs, even if
the caller passes the flag saying to pay attention to that.  (Note that
we also ignore this flag for all the non-Linux targets at present, so
there is precedent here.)
Updating re2 build to use -mmic for intel+knc builds

Following the lead of other third-party Makefiles, if we're building for
KNC using the intel compiler, throw the -mmic flag when building re2.
While here, I did some other cleanup:

* broke a long line of commands across several lines
* passed CXX into both recursive make steps just for symmetry (I don't
  believe it's used for the install step)
* removed the set of CC as it doesn't seem to be used by re2's Makefile
Merge pull request #446 from gbtitus/numCpus-on-knc

Work around lack of kernel scheduling affinity on KNC compute nodes.

The KNC compute nodes we have access to seem not to have kernel affinity
scheduling present. Either that, or perhaps it's confused: we get masks
with no bits set returned from sched_getaffinity(). To work around this
for now, just don't apply the scheduling affinity limiting in the two
functions that return the number of physical and logical CPUs, even if
the caller passes the flag saying to pay attention to that. (Note that
we also ignore this flag for all the non-Linux targets at present, so
there is precedent here.)

Reviewed by Elliot.
Merge pull request #427 from benharsh/dist-primer-lsq

Local subdomain query examples for the distributions primer
Merge pull request #447 from bradcray/re2ByDefault

Updating re2 build to use -mmic for intel+knc builds

Following the lead of other third-party Makefiles, if we're building for
KNC using the intel compiler, throw the -mmic flag when building re2.
While here, I did some other cleanup:

* broke a long line of commands across several lines
* passed CXX into both recursive make steps just for symmetry (I don't
  believe it's used for the install step)
* removed the set of CC as it doesn't seem to be used by re2's Makefile
Adding a primer for the standard module Random.

This primer intentionally does not include any functionality with Private in
the name.  It also does not include the SeedGenerators record, as that record
only includes our default random generator settings.
Add indication of the new primer to the READMEs
Add Vass's suggestions to the array vector ops primer

Vass reviewed and made a few suggestions, so implemented them here.
Updated comments with new info from c_string interface investigation.
Update arrayVectorOps.good

I forgot to update the .good after adding Vass's suggestions.
Taking Vass's comments into account.
Merge pull request #450 from hildeth/fixCStrings

Fix for io_test C compilation error.



The error message being displayed by the C compiler (GCC version 4.4.1 or newer) is
meaningful. It warns that the program is attempting to free something that is not
heap-allocated -- in this case "\n" and the definitions of other ioLiterals.

The reason why the error only appears when --fast is supplied is that aggressive inlining
brings the call to free() into the function where an ioLiteral is passed to it, so under
those circumstances the C compiler can see that something stupid is being attempted.

In the original code, the author thought is was safe to free by explicitly avoiding known
cases where the contents of a c_string was owned by another program entity. However,
since the IO module also supplies unowned c_strings it is unsafe in general to delete
them. I added comments liberally to the module code where c_strings are accessed, so
future programmers are warned away from this practice.

Looking forward, except where performance is a concern, strings should be used in
preference to c_strings. The new implementation of strings will manage memory correctly,
so the programmer who uses such objects need not concern himself with ownership details.