Merge remote-tracking branch 'upstream/master'
Merge branch 'master' of https://github.com/chapel-lang/chapel
Adding note for specifying stdin file in execopts
Initial draft of sets README
Initial draft of lsq readme
Move README.knc to platforms directory.
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-*.
Update to KNC README for release.

- Add limitations section.
- Reflect default settings in the instructions.
- Remove various notes like things
Update based on Thomas' comments
Merge pull request #476 from sungeunchoi/knc-README-update

KNC README update

- Add limitations section with most recent restrictions
- Reflect default settings in the instructions
- Update instructions for Cray machines
- Remove various notes like things
Merge branch 'master' of https://github.com/chapel-lang/chapel into cygwin-numcores
Add missing READMEs to list of READMEs.

We were missing references to README.knc, README.curl, README.auxIO
Merge branch 'master' into docFreezeReleaseREADME
Hadn't seen that README.knc had moved.  Updating its location.
Merge branch 'master' of github.com:chapel-lang/chapel into docs-lsq-readme
Adding an entry to release/README
Make Knights Corner description match the style of the others
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).