Merge remote-tracking branch 'upstream/master'
Merge branch 'master' of https://github.com/chapel-lang/chapel
Adding spec entry for HeapSort
Fixing a typo; Adding a note about the reverse argument
Initial draft of sets README
Initial draft of lsq readme
Like other third-party packages, build the static, but not dynamic gmp libs

GMP seems to be breaking on the cray-prgenv-* builds, and I think that
the attempt to build .so's is the reason.  We could selectively disable
.so's on Crays, but since we disable the .so's in every other third-party
package, why not here as well?

Thomas is going to test this branch to see whether it fixes the GMP
builds on cray-prgenv-*.
Merge branch 'master' of https://github.com/chapel-lang/chapel into cygwin-numcores
Merge branch 'master' of github.com:chapel-lang/chapel into docs-lsq-readme
Adding an entry to release/README
Merge branch 'master' of github.com:chapel-lang/chapel into docs-sets-readme
Adding an entry to release/README
Adding cygwin to the list of platforms that use /proc/cpuinfo

Cygwin has a /proc/cpuinfo, so should use the same rule as other
platforms.  Unfortunately, it doesn't have a 'siblings' entry
(at least for my laptop), so it doesn't work.  We may have better
luck on the official test platform.  In any case, this is a
step in the right direction.

I've proposed to Greg that we should make the default case
optimistically use /proc/cpuinfo rather than making it an
error case so that other platforms that support /proc/cpuinfo
will work without human intervention (and if they don't work,
a similar amount of developer intervention is required as if
it gets a cleaner error message).
Formatting changes
Adding a reference to the dist primer; minor style changes
Merge pull request #481 from bradcray/cygwin-numcores

Adding cygwin to the list of platforms that use /proc/cpuinfo for this test

Cygwin has a /proc/cpuinfo, so should use the same rule as other
platforms.  Unfortunately, it doesn't have a 'siblings' entry
(at least for my laptop), so it doesn't work.  We may have better
luck on the official test platform.  In any case, this is a
step in the right direction.

I've proposed to Greg that we should make the default case
optimistically use /proc/cpuinfo rather than making it an
error case so that other platforms that support /proc/cpuinfo
will work without human intervention (and if they don't work,
a similar amount of developer intervention is required as if
it gets a cleaner error message).
Fixing a typo
Merge pull request #482 from benharsh/docs-lsq-readme

Docs: Local subdomain query readme
Merging with chapel-lang:master
Style/wording improvements