Add new WARNINGS var in Makefiles. Set to 1 when CHPL_DEVELOPER is defined.

WARNINGS will be used to enable and disable compiler warnings in
make/compiler/Makefile.* files. At present, those Makefiles enable and disable
warnings based on CHPL_DEVELOPER. There are situations where CHPL_DEVELOPER is
not set, but compiler warnings are wanted.
Use WARNINGS to enable warning flags in compiler specific makefiles.

Previously whether or not CHPL_DEVELOPER was defined determined if the warning
flags were added for C compiler. Instead, use the WARNINGS variable. This
allows a developers to build with compiler warnings enabled (e.g. when building
the runtime/) without the rest of the CHPL_DEVELOPER settings. Conversely, if
CHPL_DEVELOPER is set, a developer can disable C compiler warning flags by
setting WARNINGS=0 when calling make. The latter is not especially useful (or
recommended).
Copy .bash versions of setchplenv to .zsh version.
bash -> zsh
Merge branch 'master' of github.com:chapel-lang/chapel into add-warnings-opt
Update documentation for new WARNINGS variable in makefiles.
Cleanup output of .sh versions of setchplenv.

Use printf to print strings that should not have a new line char. I copied the
.bash versions and substitued `printf` for `echo -n`.
Add %s format argument to printfs
Update the string shootouts so that they will recognize the unused input value
sent to them through the Computer Language Benchmarks Game test suite.
Add chmod capability.

This allows the user to call a Chapel-style version of chmod to modify the
current permissions of a file or directory.  I added the interface to the
FileSystem module and the backend support to chpl-file-utils.c/.h, reserving
the name in reservedSymbolNames since it will conflict with the C definition
otherwise.  I also added two tests: one that the function works on both files
and directories, and one that a correct error message is generated when called
on a non-existent file.
Whoops, forgot a line break!
Merge pull request #619 from bradcray/triage-sep-blc

Updating REGRESSIONS based on past several days

new regressions:
- lulesh-dense started failing in valgrind -- Sung was unable to reproduce
- noted cases in which I/O is dropped on the floor for CCE
- a few new cases of glob() failing with CCE for similar reasons to what we've seen elsewhere

new fixes:
+ maxTaskPar is now working on cygwin (thanks Greg!)

misc:
* a few other things came and were fixed -- these can be seen in the commits that make up this pull request
* noted other noisiness / annoyances in preparation for REGRESSIONS week
Re-futurizing this future, but skipping it for segment 'fast'
This is a clone of remoteString3, tested only for segment 'fast'

When the original future passes, this test should be removed,
along with the .skipif on the original.
Fix baseline log locations.
Merge pull request #620 from bradcray/remoteString3-future-edits

Edits to David's remoteString3 test

[reviewed by @daviditen]

David's remoteString3 future recently started passing for gasnet-fast
testing, so Sung unfuturized it. However, it still seems to fail for
gasnet-everything. For that reason, I'm refuturizing it, but with a
skipif to avoid false positives in the gasnet-fast case. Simultaneously,
I've added a clone of the test to lock in the gasnet-fast behavior since
it's working there for the time being. I have a question out to Sung
wondering what would cause the difference.

When remoteString3.future is retired, its skipif should be removed,
as should the new remoteString3-seg-fast.chpl test.
Reduce some GMP memory leaks using explicit frees.

Call delete on BigInt (class) instances to release them.

Call mpz_clear() on mpz_t instances to release them.
Merge pull request #621 from thomasvandoren/fix-baseline-test-log-location

Fix baseline log locations.

Fix baseline log location for nightly testing. This broke in #600.
Merge pull request #622 from hildeth/gmpMem

Reduce some GMP memory leaks using explicit frees.

Call delete on BigInt (class) instances to release them.

Call mpz_clear() on mpz_t instances to release them.

[Not reviewed.]
Add note to definition of ENOERR indicating that it represents the state where
no error has occurred.