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
Default uses: Centralize the logic for setting module uses
Use the centralized method to insert module uses
modules/internal: Remove the ChapelStandard pragma from internal modules
Test all the module dirs for copyrights.
Merge branch 'master' of https://github.com/chapel-lang/chapel into update-check-copy-test
Add note about add_licence_to_source.py script in error output.
Add copyright to -ipe and -minimal module files.
Added other task intents.
Add copyright to modules-ipe
Gather performance data for the release version of HPL with MAX_LOGICAL

To avoid cluttering the release directory with files that are only relevant to
those interested in the performance implications of different
CHPL_RT_NUM_THREADS_PER_LOCALE, a new directory named perfComp has been made in
test/studies/hpcc/HPL/.  This directory contains symlinks to the portions of the
test that do not need to change between the two versions (the source code, the
.good file, the perfkeys and HPCCProblemSize), with alterations made to the
.perfexecopts file such that the two versions will not overwrite each other's
data.  Since this test is only interesting for performance runs (and should
always match the behavior of the original, being a symlink), add a skipif which
will only run when the performance flags have been thrown (at the moment, this
hard-codes --fast and --static into the compopts).

Additionally, add a suite to the performance graphs to display all tests which
are run with a different CHPL_RT_NUM_THREADS_PER_LOCALE value, in comparison to
their default runs.  This suite will soon contain more than just HPL.
start_test -performance thought the two hpl versions would match

Even though I specifically put a different .dat file in the execopts.  Ah well.
Move the files so that the names don't collide any more.
Gather performance data for NPB EP with MAX_LOGICAL

Similar to the HPL addition, made a separate directory for performance runs with
MAX_LOGICAL over a symlink of the original test, which will be skipped for runs
other than performance trials.

Add this new data to the EP graphs, and the EP graphs to the MAX_LOGICAL suite.
Merge pull request #1043 from noakesmichael/mod-uses

ModUses: Add logic to avoid need for ChapelStandard pragma in Internal

We worry about inserting module-use updates in two places; ChapelBase needs a use for
_root, and modules outside internal should automagically get a use on ChapelStandard.  I
provide a method on ModuleSymbol to handle this and retired the code that was in
passes/filesToAST.cpp

I then pulled the "do not add ChapelStandard" pragma off the modules in modules/internal and
modules-minimal/internal.

Happened to notice that modules-minimal/internal did not have the copyright notice.  Added it
to modules-minimal and modules-ipe

Compiled: STD clang/darwin, STD gcc/linux64, LLVM gcc/linux64
Tested: paratest --verify
Review: none
Gather performance data for EP STREAM fragmented with MAX_LOGICAL

Similar to the HPL and EP additions, made a separate directory for perf runs
with MAX_LOGICAL over a symlink of the original tests, which will be skipped
for runs other than performance trials.

Add this new data to the EP STREAM fragmented graph, and the graph to the
MAX_LOGICAL suite.
AstDumpToNode: Tweak format for TypeSymbol
Gather performance data for the release fannkuch version with MAX_LOGICAL

Similar to the prior three commits, adds a performance directory populated by
symlinks to the files associated with the original version, which will only do
performance runs and uses CHPL_RT_NUM_THREADS_PER_LOCALE=MAX_LOGICAL.  Add the
new numbers to the fannkuch graph and the graph to the suite for MAX_LOGICAL