Merge branch 'master' of github.com:chapel-lang/chapel into test
Merge branch 'master' of github.com:chapel-lang/chapel into test
Remove --ignore-internal-modules flag and associated tests
various style changes; using atomics instead of reducing arrays
minor style fixes
Merge pull request #34 from benharsh/fannk

Fannkuch cleanup to improve style and use atomics
Move stack declarations for aprun argument list to global scope.

These declarations were previously at the global scope, but I had
moved them on to the stack in my previous commit (r23802 in the SVN
world) because my original design was to copy them before returning.
I decided to keep the design that was originally there before my
commit, but forgot to move the local declarations back to the global
scope.

This worked in local testing likely because I did not build optimized.
Merge branch 'master' of github.com:chapel-lang/chapel into aprun-launcher-fix
Fix generic resolution of more complicated types with noinit
Make the variables static as they were originally
Not yet tested.
Merge pull request #36 from sungeunchoi/aprun-launcher-fix

Move stack declarations for aprun argument list to global scope.  Fixes aprun launcher issues.
Merge branch 'master' into kill_test_module_sort_future
Merge pull request #31 from sungeunchoi/test

Remove --ignore-internal-modules flag
Fix bug in cache
Stop adding duplicate fences in waitFor

Fences I added here are also added by the compiler
when --cache-remote is enabled, but they don't do
anything if --cache-remote is not enabled, so they
don't need to be explicitly included here.
Relax task counting fences, add barrier fence

The task counting atomics don't need to imply fences
as these are handled elsewhere and we're really just
updating a counter.

For the barrier here, it's waiting on (not atomic)
local memory to change from a remote locale's put - which
is not legit according to the memory model... add
a fence (but I'd like to see a better barrier).
Change a warning to an error.  Previously, we had only warned if a function
specified its return type but did not return a value along one of its control
flow paths.  This will cause unpredictable behavior when return temps do not
initialize themselves by default (relying on other assignments to initialize).
Now, the behavior will be deterministic and will correctly not allow the
program to execute.
Update the previously known test case affected.

The test functions/hilde/retTypeNoRet.chpl displayed the warning behavior
described in the previous commit.  Since the test now fails to compile, I have
altered the .good file accordingly, and modified the test to only include the
minimum calls which will generate the error message.
file and channel types require that one of their fields in particular has been
initialized whenever an instance has assignment performed on it, therefore it
is not possible to use noinit with these types.