Adding spec entry for HeapSort
Fixing a typo; Adding a note about the reverse argument
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-*.
Initial draft of associative implicit addition section for spec
Filter the --enable-static/--disable-shared flags only for Cray platforms

This should make the C compile-time warning go away for Mac while
avoding building the .so's on Crays.  It's also most similar to what
we've been testing by default for the past several months.
Skip pidigits if --llvm is a COMPOPTS flag.
Minor cleanup of README.curl

Make the lines 80 characters long.  Add an apostrophe to
(2) Bindings to libcurl's curl_easy_setopt and curl_easy_perform
Revert "Skip pidigits if --llvm is a COMPOPTS flag."

This reverts commit 7fda53560785eeec13c165e43f303bce60a26707.
Disable gmp when running llvm tests.

suggested by @lydia-duncan
Update to reflect changes related to number of threads.

Document the new symbolic string values 'MAX_PHYSICAL' and 'MAX_LOGICAL'
for CHPL_RT_NUM_THREADS_PER_LOCALE.  Change terminology to talk about
physical CPUs and logical CPUs instead of cores and hyperthreads.
Merge pull request #488 from gbtitus/doc-symbolic-CHPL_RT_NUM_THREADS_PER_LOCALE

Update to reflect changes related to number of threads.

Document the new symbolic string values 'MAX_PHYSICAL' and 'MAX_LOGICAL'
for CHPL_RT_NUM_THREADS_PER_LOCALE. Change terminology to talk about
physical CPUs and logical CPUs instead of cores and hyperthreads.

Not reviewed.
Merge pull request #487 from thomasvandoren/disable-pidigits-for-llvm

Disable pidigits for llvm

suggested by @lydia-duncan
Minor edits to README.auxIO

Makes sure the lines are at most 80 columns long, removes a reference to the
non-existent README.lustre, and switches "no one" to "no individual" in the last
entry, as I believe it is clearer this way.  Everything else looks fine.
Revert "Disable pidigits for llvm"
At Thomas's suggestion, extending the filter to include cray-x*

(in order to avoid disabling for cray-cs, which can probably
better handle the .so's).
Merge pull request #490 from chapel-lang/revert-487-disable-pidigits-for-llvm

Revert "Disable pidigits for llvm"
Snapshot of REGRESSIONS updates since last night
Add '-N 1' to the aprun command for KNC as we do for other node types.
Merge pull request #491 from bradcray/triage-sep-blc

Snapshot of REGRESSIONS updates since last night

Failures:
* new compilation issue for Sung's memLeaks/promotion (should now be fixed)
* lingering regression for memLeaks/coforall for GASNet only (sungeun)
* pidigits failing on llvm due to enabling that combination for the first time (expected)
* filerator/walk failing on cygwin due to missing /bin/sh (can't reproduce)

Improvements:
* Vass's sync/single by generic regressions fixed (but still lingering on a few platforms due to lag in testing -- moved them down to the appropriate categories for tracking)
* Lydia's case-sensitivity darwin regressions fixed (but still listed on cygwin due to testing lag)
* miniMD fixed on darwin for reasons I don't understand (maybe I misdiagnosed?)
* regexp_channel_test working on cygwin for reasons I don't understand
Remove --no-bounds-checks compopts from "maximal" range tests

This removes the --no-bounds-checks compopts from
  test/trivial/deitz/test_max_range_iteration
  test/types/range/elliot/test_min_and_max_range_iteration

The original intent of having the explicit --bounds-checks and
--no-bounds-checks was to not have to worry about what the test would do
normally vs for --fast testing. The no-bounds-checks versions were expected to
overflow and cause an infinite loop that the test program would detect.
However, since these two tests would result in signed overflow and signed
overflow is undefined in c anything can happen. For most compilers this did
result in infinite loops, but for the cray compiler the tests stopped like you
would expect a regular loop to, which was a little surprising at first but is
fine since the behavior is undefined.

types/range/hilde/maximalRange did not need to change since unsigned
integer overflow is well defined.