I have fixed the command line parsing problem for cfd-mini-c
Merge remote-tracking branch 'upstream/master'

Conflicts:
	test/studies/colostate/cfd-mini-c.execopts
Update chpl_platform.py to support cygwin32 and cygwin64.

Cygwin now supports both 64bit and 32bit versions. Update chpl_platform.py to
distinguish between 32bit and 64bit in the same way linux32 and linux64.

Tests and documentation will need to updated to reflect the new name.
Add Makefile.cygwin{32,64} files that just include Makefile.cygwin.
Move scope of machine up to be more accessible in chpl_platform.py.
Fix makefile include paths.
Update cygwin comparisons in util/chplenv/
Update testRelease to use chpl_platform.py.

testRelease was duplicating some of the logic for detecting platform, so just use chpl_platform.py.

Also fix comparison against cygwin in nightly.
Add symlinks for runtime/include/cygwin{32,64}/.

Both cygwin32 and cygwin64 have symlinks to runtime/include/cygwin/.
Fix stdin support when multiple lines in .execopts.

Previously, a .execopts file like the one below would successfully run with
green.txt, but would fail when running the second configuration for red.txt:

```
< green.txt  # cond.if.green.good
< red.txt    # cond.if.red.good
< yellow.txt # cond.if.yellow.good
```

Error message:

```
...
[Executing program ./cond.if  < green.txt]
[Executing diff cond.if.green.good cond.if.0-1.exec.out.tmp]
[Success matching program output for /Users/tvandoren/src/pytochpl/docs/source/examples/cond.if]
[Error: a redirection file already exists: green.txt]
```

The error is coming from the second iteration of the .execopts loop because the
stdin file is not reset with each loop.

Update sub_test to track when stdin file is modified by .execopts and reset at
the beginning of each .execopts iteration.
Fix typo: x64_64 -> x86_64
Add copyrights to new makefiles.
Update docs and .skipifs for new cygwin platform vals.
Merge pull request #956 from thomasvandoren/fix-sub-test-stdin-multiple-execopts

Fix stdin support when multiple lines in .execopts.

Previously, a .execopts file like the one below would successfully run with
green.txt, but would fail when running the second configuration for red.txt:

```
< green.txt  # cond.if.green.good
< red.txt    # cond.if.red.good
< yellow.txt # cond.if.yellow.good
```

Error message:

```
...
[Executing program ./cond.if  < green.txt]
[Executing diff cond.if.green.good cond.if.0-1.exec.out.tmp]
[Success matching program output for /Users/tvandoren/src/pytochpl/docs/source/examples/cond.if]
[Error: a redirection file already exists: green.txt]
```

The error is coming from the second iteration of the .execopts loop because the
stdin file is not reset with each loop.

Update sub_test to track when stdin file is modified by .execopts and reset at
the beginning of each .execopts iteration.

r: @benharsh
Merge pull request #952 from cathieO/master

Command line parsing in cfd-mini-c fixed

The command line parsing wasn't working because it did not check for unwanted command arguments.
Turn of warning when stdin redirection isn't supported

start_test auto detects when stdin redirection isn't supported and warned the
user that it was going to skip tests with stdin. The warning proved move
annoying than useful especially since it made things like 'make check' fail.
This removes the warning and just turns it into an 'Info' message. The user
won't see it reported at the end of test summary but that seems fine.
Add better execution timing when using launchcmd

sub_test times program execution. However, this number is inaccurate for
launchers that use a queueing system such as qsub/pbs and slurm. This number is
going to be particularly bad for tests that spend a long time in the queue
(such as our performance tests that run concurrently and request specific
nodes.) This adds some functionality to chpl_launchcmd to time once the
queueing system reports that the program has actually started running and once
it's done and puts that time in a file that sub_test then reports.

This number still isn't going to be too accurate since we can't poll the
queueing system that often. An accurate way to accomplish this would be to have
the launchers support a way to wrap the executable with a timer, and have that
timer report the results. That's more work than I want to do right now,
although it's probably the right way if we start doing multi-locale performance
timing for whole programs.
Add check to make sure launchcmd is being used to be sure var is set
Merge pull request #957 from ronawho/multi-locale-test-improvements

Turn of warning when stdin redirection isn't supported

[ok'd by @bradcray @thomasvandoren]

start_test auto detects when stdin redirection isn't supported and warned the
user that it was going to skip tests with stdin. The warning proved move
annoying than useful especially since it made things like 'make check' fail.
This removes the warning and just turns it into an 'Info' message. The user
won't see it reported at the end of test summary but that seems fine.
Fix termination condition for getNextExpr