Remove calls to compiler warnings after we've printed out the message. No reason to generate that code.
Merge branch 'master' of github.com:chapel-lang/chapel into remove-comp-warning
Removing debugging printf; Adding some comments
Updates based on this morning's returns
Fix --walltime parsing for sub_test

When passing --walltime to the executable (for slurm and pbs) the string we
created was only valid for times under 100 minutes. After that it became
invalid. We never run into this in nightly testing, but I ran into it when
trying to see how long hpl release would take to finish for gasnet+mpi
Place removeCompilerWarning in pruneResolvedTree
Wrapping up my REGRESSIONS week
Merge pull request #1052 from bradcray/triage-blc-dec-2014

Wrapping up triage week

Improvements
-------------------
* thomasvandoren/enumerate has now worked its way out of the system, so removed it

Regressions
-----------------
* none!  (Well, OK, we had some, but they got fixed before I had a chance to commit...)

Misc
------
* completed the "review" sweeps for my week
* removed sporadic failures that hadn't been seen in a month as housecleaning
* factored 32-bit failures away from linux32 and cygwin32 because cygwin32 wasn't as much a proper superset of linux32 as I'd hoped (and as the "Inherits" tag suggests to me).  Once we got this category down to zero, I'd be inclined to remove it again.
* removed notes on investigative work, as I believe that belongs in pivotal, not here (to keep short and sweet)
* removed a duplicate (and unlabeled) reference to meteor-fast, as it's inherited from a parent category
Merge pull request #1051 from benharsh/remove-comp-warning

Remove compilerWarnings after they have been issued

This patch removes compilerWarnings at the end of function resolution, after they have served their purpose. When they were left in the program, we would leak the string every time the function was called.
Removing comments dating from this test's days as a future at Lydia's request
Merge pull request #1053 from bradcray/removeQuestions

Removing comments from test's days as a future at Lydia's reqest
Filing an internal error caused by indexing into an integer type

This test was sent by Chris Wailes to chapel-developers on
Apr 22, 2014 and, from what I can see, was never filed against
the testing system.  The error message proposed here is just a
placeholder.  I'm open to other        sufficiently clear user  (rather
than internal) messages   as well.
Fleshing out .future
Merge pull request #1055 from bradcray/index-int-future

Filing an internal error caused by indexing into an integer type

This test was sent by Chris Wailes to chapel-developers on
Apr 22, 2014 and, from what I can see, was never filed against
the testing system.  The error message proposed here is just a
placeholder.  I'm open to other	sufficiently clear user	(rather
than internal) messages	as well.
AstDumpToNode: Tweak output
Merge pull request #1057 from noakesmichael/dump-0

AstDumpToNode: Refine the output for some cases

Compiled: STD clang/darwin, STD gcc/linux64, LLVM gcc/linux
Tested: paratest --verify (Not really needed since this only a debugging mode)
Review: none
Args: Update compute_program_name_loc to take ArgumentState* as an arg and simplify
Args: Rename arg_state to sArgState
Drop chplBinaryName; rely on sArgState.program_name
Args: Rename compute_program_name_loc() to init_args() and move it to arg.cpp.  Call init_args before main AST init