Remove self comparisons in test/extern/ferguson/c_ptrs.chpl

c_ptrs.chpl had comparisons that looked like:

assert(my_ptr == my_ptr);

These now check that my_ptr != c_nil. I added a couple of overloads in
SysBasic to allow comparison between c_ptr and c_void_ptr to let us do
this.
Snapshot -- got 3D working, but broke 1D
This version works for 1D and 3D again
Fix overlapping memory in memcpy() reported by valgrind.

This was a slam-dunk.  I replaced every direct call to memcpy() in our runtime code with a
call to chpl_memcpy(), then defined the latter as an always-inlined function that calls
through to the real memcpy().

The symptoms of the valgrind error are that the source and destination address are the
same (as I suspected).  So I added an assert for that error case and tracked down the
caller.  In chpl_gen_comm_get, there is the possibility that the source and destination
address are the same, if the data being fetched resides on the same locale.  That is where
I fixed the problem.

It would be possible to also fix the problem in the calling module code, but there we
would have to add a primitive to perform pointer comparison.  It is far easier to do this
in the runtime code.

I concluded that it would be helpful to leave the chpl_memcpy wrapper in place.  If NDEBUG
is true, then the assert will expand to nothing, and the whole routine will inline to a
direct call to memcpy.  So the runtime cost of this extra code should be nil (with
optimizations enabled).
Remove the refvar keyword

Remove refvar from the language, replacing it with the ref keyword.

Doing this requires removing the deprecated `ref(var1,var2)` task intent
syntax. Using that form will now be a syntax error rather than a
warning.

While there I cleaned up buildVarDelcs to take in a set of Flags to
apply to the variable, rather than passing them through three different
variables that would often just be set to FLAG_UNKNOWN and ignored.
Update tests to use  instead of
Cleanup.  Now passes testing.
Can't see why 1D and 3D should be treated differently here.
Add case to lock in 3x3x3 error that's been around forever
Removing debug printing from today's session
Removing Sung's lulesh studies test

With the bug fixes of the earlier commits here, I verified that the
release version subsumes Sung's version and outperforms it when
compiled in the similar configuration (probably due to using atomics
rather than syncs).  Given that this test is now redundant and that
we're getting timeouts on it in many configurations, I think it's time
to remove it.
Remove a future file, it was resolved yesterday

Yesterday, I made our domain debugging output cast its message to the leak-free
string record implementation in order to silence some baseline failures.  Turns
out this was the reason this future was still failing (though I suspect that
Mike resolved the actual problem earlier).  I made a note in the test itself
about the expected output (it still says it leaks 8 bytes but that's because a
global array is now longer than it was before, and that array will be taken care
of upon completion of the test), and removed the skipif as this test does work
with CHPL_COMM=gasnet.
Merge pull request #751 from lydia-duncan/resolveFuture

Remove a future file, it was resolved yesterday

Yesterday, I made our domain debugging output cast its message to the leak-free
string record implementation in order to silence some baseline failures. Turns
out this was the reason this future was still failing (though I suspect that
Mike resolved the actual problem earlier). I made a note in the test itself
about the expected output (it still says it leaks 8 bytes but that's because a
global array is now longer than it was before, and that array will be taken care
of upon completion of the test), and removed the skipif as this test does work
with CHPL_COMM=gasnet.
Updated according to comments from gbt:

Moved the src==dest test out of chpl_gen_comm_get() and into chpl_memcpy().

Adjusted indentation in chpl-cache.c, due to wider function name (chpl_memcpy vs. memcpy).

diff --git a/runtime/include/chpl-comm-compiler-macros.h b/runtime/include/chpl-comm-compiler-macros.h
Merge pull request #748 from Kyle-B/kb-refvar-to-ref

Remove the refvar keyword

Remove `refvar` from the language, replacing it with the `ref` keyword.

Doing this requires removing the deprecated `ref(var1,var2)` task intent
syntax. Using that form will now be a syntax error rather than a
warning.

While there I cleaned up buildVarDelcs to take in a set of Flags to
apply to the variable, rather than passing them through three different
variables that would often just be set to FLAG_UNKNOWN and ignored.
Merge pull request #743 from Kyle-B/kb-remove-self-comparison

Remove self comparisons in test/extern/ferguson/c_ptrs.chpl

c_ptrs.chpl had comparisons that looked like:

assert(my_ptr == my_ptr);

These now check that my_ptr != c_nil. I added a couple of overloads in
SysBasic to allow comparison between c_ptr and c_void_ptr to let us do
this.
Merge branch 'fixMemcpyOverlap' of github.com:hildeth/chapel into fixMemcpyOverlap

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
Merge pull request #750 from bradcray/lulesh-bugfix

Lulesh release bug fix and retire Sung's version

[reviewed by sungeun]

This commit retires Sung's study version of LULESH and fixes
a bug in the release version when using the 3D representation.

Sung's version of lulesh has been timing out in certain
configurations, which raised the question of whether it's
still valuable or not. Sung's version (previously Brandon's
version) was the origin of the release version, which
expanded upon it by trading the 3D-only format for a
1D or 3D with sparse or dense materials array. Comparing
the sources, the two looked very similar, so it seemed
reasonable to retire Sung's version.

However, before doing so, I wanted to make sure that the
release version outperformed Sung's and, in doing so,
found that the 3D version had a bug in the release (and has
since we introduced it). The reason we didn't notice this
is that at some point we dialed the correctness problem size
down to a 2x2x2 grid (which matched an input file that the
original authors gave us) in which every node is a boundary
case, and therefore the bug was not exhibited. By running
on even a 3x3x3 case, the bug was seen.

The fix was an off-by-one error caused by a coordinate
translation routine that wasn't debugged fully for 1D and
3D cases and turned out to be pretty easy to implement.
While taking that on, I also took out some overly complicated
code that treated 1D and 3D differently for no good reason
that I could tell. I also fixed some debug printing that had
not been made portable for the 3D case.

One of the reasons that these problems went undetected
is that the 3D version isn't really in the spirit of the benchmark,
so it's not what we've been focusing on. Thus, while this
bug was unfortunate, it doesn't invalidate any previous
experimental results that we've reported on (which focused
on 1D representations only).
Updates based on today's runs
Updating stories based on what I think is passing