Add vanilla intel cc testing for knc.

It just tests that make succeeds. It makes no attempt to actually compile or run a program...
Revert "Set runtime stack size to 2M for 32bit platform in smoke test."

This reverts commit bde1b76f1025cd01511b728ec7efe7c620eac92f.

linux32 was fixed by cee911bf5a
Add real comments to yields in qthreads sync var lock and unlock

These were added to resolve deadlock that cropped up when we switched to the
nemesis scheduler. I never commented them properly because we weren't sure it
was the final solution or if the values were good. Things seem to be in good
shape some I'm adding extensive comments.
Merge pull request #259 from thomasvandoren/update-linux32-build-script

Revert "Set runtime stack size to 2M for 32bit platform in smoke test."

This reverts commit bde1b76.

linux32 was fixed by cee911b

requested by @ronawho
Adding future for type mismatch for autocopy functions with ref arg
Merge pull request #261 from sungeunchoi/test

Adding future for type mismatch for autocopy functions with ref arg

bug: Compiler internal error for record autocopy functions that take a ref arg

recordWithRefCopyFns.chpl:25: internal error: actual formal type mismatch for chpl__autoCopy: myR != _ref(myR) [checks.cpp:627]
Unload all craype-intel-knc conflicts for vanilla test script.

suggested by @ronawho
Merge pull request #254 from thomasvandoren/test-vanilla-intel-knc

Add vanilla intel cc testing for knc.

It just tests that make succeeds. It makes no attempt to actually compile or run a program...

reviewed by @ronawho
FATAL error generated from compiler for type int.

Compiler generates a FATAL for the following program

var sum1 = 0.0;
var sum : int = 0;

sum1 = 4.0;
sum = (int)(sum1);

internal error: FUN5894 chpl Version X.XX.X

Compiler treat (int) as a constructor call for int taking
a real argument.  This should generate an error message.
Merge pull request #262 from tmacd9/fatal

FATAL error generated from compiler for type int.

Compiler generates a FATAL for the following program

var sum1 = 0.0;
var sum : int = 0;

sum1 = 4.0;
sum = (int)(sum1);

internal error: FUN5894 chpl Version X.XX.X

Compiler treat (int) as a constructor call for int taking
a real argument. This should generate an error message.

[reviewed by diten]
Switch to hwloc v1.9.1 as default.
See the performance implications of qthreads without hwloc
Merge pull request #263 from ronawho/qthreads-as-default

See the performance implications of qthreads without hwloc
Stop performance testing if OPTIMIZED=1 build failed

* If the compiler OPTIMIZED=1 build fails, turn off compiler perf testing.
* If the runtime OPTIMIZED=1 build fails and it is a performance test run, it
  is a fatal error, so send the failure message and exit.
* Added the ability to exit on a fatal error back to mysystem after it was
  accidentally removed in a previous commit.

Tested by doing: nightly -debug -performance -notest
with and without things to warn about added to the compiler and runtime.
Merge pull request #265 from gbtitus/hwloc-1.9.1-is-default

Switch to hwloc v1.9.1 as default.

Reviewed by @bradcray, @sungeunchoi, @ronawho over email.
Wordsmithing based on gregs review
Merge pull request #260 from ronawho/qthreads-syncvar-deadlock

Add real comments to yields in qthreads sync var lock and unlock

[reviewed by @gbtitus]

These were added to resolve deadlock that cropped up when we switched to the
nemesis scheduler. I never commented them properly because we weren't sure it
was the final solution or if the values were good. Things seem to be in good
shape some I'm adding extensive comments.
Turn off guard pages for stress/deitz/test_10k_coforall

I see this test timeout sometimes when I do a paratest when other people are
also testing. It creates a lot of small tasks so it makes sense to turn off
guard pages for it.
Unify stress and stress.numthr execopts and turn off guard pages

There are two versions of this test because we don't have a way to use a
different execenv for a single test. I believe they are intended to be
identical so I made the execopts the same.

This also turns off guard pages for both as it is a stress test that creates a
large number of tasks and takes a long amount of time to complete with guard
pages. stress.numthr already had guard pages off but as a compopt instead of
as part of the execenv.

The compopts is nice because it's general and the way we want users to do it,
but the execenv is nice because you don't have to copy it for each compopt. For
now I decided to stick with using QT_GUARD_PAGES=false over the compopt, and
once CHPL_STACK_CHECKS also backs whether guard pages are used at execution time
I will replace all uses of QT_GUARD_PAGES
Copied the execenv, but didn't clear the unwanted env vars