Initial support for specifying stdin file in execopts
Using execopts stdin file for knucleotide
Using execopts stdin file for reverse-complement
Merge branch 'master' into stdin-in-execopts
Produce an error if a .stdin file exists and one is specified in execopts
Update prediff-for-aprun-with-moab to filter more generally.

Removes absolute filepath and line number from grep filter. This came about when we moved testing from one system to another.
minor cleanup of glob iterator
Using execopts stdin for regex-dna
Merge pull request #97 from tzakian/parallel-glob

Minor cleanup of glob iterator
Merge pull request #98 from benharsh/stdin-in-execopts

This patch modifies sub_test to support specifying the stdin file inside an *execopts file.

Three shootout benchmarks (k-nucleotide, regex-dna, and reverse-complement) use the output of the fasta benchmark as input.

The size of the input files we need for performance testing is far too large to keep in the repository (50MB to 250MB). A later patch will support the generation and cleanup of these files during testing.

However, once we have these generated files, we would still need to create .stdin files so our test scripts would use them as standard input. Making copies of these files would take up a lot of space, and using links is unattractive. Both might be difficult to clean up.

The solution here is to allow for the stdin file to be specified inside an *execopts file. If the second-to-last argument is '<', then this patch will attempt to use the last argument as the stdin file.

Another benefit of this change is that we can have just one correctness input file per shootout, instead of one per .chpl test.

This change has passed paratest.

Reviewed by lydia-duncan
Merge pull request #96 from thomasvandoren/update-aprun-prediff

Update prediff-for-aprun-with-moab to filter more generally.

Removes absolute filepath and line number from grep filter. This came about when we moved testing from one system to another.

r: @hildeth
Adding futures tests
Merge pull request #100 from tzakian/parallel-glob

Adding futures for:

* Recursive parallel iterators
* Calling functions that construct the type of the method calling them (e.g., file.foo() calling open)
* Calling functions that construct the type of the iterator calling them (e.g., file.iter() calling open)
Make string_length() and string_compare() static inline functions, as
they simply call the corresponding C library functions.
Change declaration formatting for string_length() to match the others
as per Mike's suggestion.
Merge pull request #101 from sungeunchoi/test

Make string_length() and string_compare() static inline functions

[reviewed by Mike]

The runtime functions string_length() and string_compare() simply call the corresponding C library functions, so this commit makes them static inline.

The actual motivation for this change is due to a gcc error/warning from throwing the flag -Werror=free-nonheap-object under some configurations, e.g., CHPL_COMM=gasnet with CHPL_GASNET_SEGMENT=everything. The code in question is in chpl_free_c_string() and is protected by a conditional that checks the length of the string. In the offending case, the memory is guaranteed to be on the heap unless the length is 0, but the length check is made via string_length() which was off in the bowels of the runtime library. Making string_length() static inline makes gcc happy.
Adding another test to ensure that the user can make use of pre-defined
_defaultOf functions.
Merge pull request #103 from lydia-duncan/addDefaultOfTest

Add another test for _defaultOf functionality [trivial]

This test ensures that the user can make use of pre-defined _defaultOf functions.
Fixed the "matching .bad" errors in field-in-task-ref-clause.chpl
Merge pull request #105 from vasslitvinov/fixMatchingDotBadErrors

Fixed the "matching .bad" errors in field-in-task-ref-clause.chpl

The .bad mismatch was due to .bad generated with --verify,
while out tests run without it.

I think for this test the outcome is more predictable when the bug
is caught by verification, rather than in whatever way the compiler
happens to trip over it. So I am adding --verify to compopts.