Attempt to fix the recent "continually re-make version.cpp" issue

This commit attempts to fix the recent problem that Sung has been
complaining about in which version.cpp is continually re-built.
Though I have not seen it on my desktop, I am seeing it on my
personal Mac which permitted me to debug it.  I'm wondering if
there could be a sensitivity to Perl version number at play here?

From what I could tell, the BUILD_VERSION file has been storing the
git SHA value as a string literal with quotes (e.g., "abcdef" would
appear in the file.  This was compared against a string without qutoes
(e.g., abcdef) and returned false, so it would create a new
BUILD_VERSION file.

The approach I took here was to move the quotes out of the
BUILD_VERSION file and place them into the version_num.h file.  It
surprised me a little that this worked because I thought C didn't
generally like multi-line string literals, yet it does, at least on my
Mac's version of gcc.  It would be good to do some more testing on
newer gcc's before merging back to master.
Merge branch 'master' of https://github.com/chapel-lang/chapel into nbody-work
Tucking away a version of the release nbody that uses ref[var] variables
Tucking away these changes which inline more constructor stuff

[this change is highly speculative]

This should be double-checked before committing it, but I think
what I've done is to inline the setup of ranges and of other
default-constructed records.  My thinking was to give the C
compiler more information (and also make it simpler for me to
read in the generated code what was happening when ranges are
created.
Change the flags sent to gcc

This is speculative and not ready to be merged into trunk.

In some of the hand-edits I was doing, I needed these changes,
I think primarily so that I could try mixing declarations and
computations.
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).
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
Skip testing multilocale lammps/lsms files under comm=none.
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.
Updates based on today's runs
Updating stories based on what I think is passing
Merge pull request #757 from bradcray/triage-sep-blc

Updating REGRESSIONS from past 24 hours or so

New errors
----------
* LeakedMemory5 is now not finding its suppression (probably fixed with
  Lydia's baseline string leaks fix -- have alerted her)


Resolved errors
---------------
* Removed pervasive I/O sporadic failures from x?-wb.* category, as they
  seem to be cleared up (thanks Mike!!!)

* Removed lulesh failures from x?-wb.prgenv-cray as they seem to have
  self-resolved (due to the above?  Or something else?  Thanks masked man!)

* Removed baseline failures due to different amounts of string data leaked
  (thanks Lydia!)

* StringImpl/memLeaks/promotion also seems fixed (thanks Lydia!)


Misc
----
* moved StringImpl/memLeaks/coforall down to gasnet.fifo as that's the only
  place I ever see it fail

* noted compopts addition to parSafeMember test
Merge pull request #746 from hildeth/fixMemcpyOverlap

Fix overlapping memory in memcpy() reported by valgrind.

Replaced every direct call to memcpy() in our runtime code with a
call to chpl_memcpy(), then defined the latter to return the dest argument if dest == src and otherwise call the real memcpy().
Back dest==src test out of chpl_memcpy().

When -Werror=uninitialized is tossed, GCC complains about the version of chpl_memcpy()
where memcpy() is called only if dest and src differ.  It apparently does not reason that
dest is valid since it is already equal to src.  So I backed out the aggressive
conditional call to the system memcpy, and instead moved the dest != src test back to
chpl_gen_comm_get().

I also noticed that code used in building the launcher cannot see the definition of
chpl_memcpy(), so I reverted those calls to being direct calls to the system memcpy().

TODO: We may still get hung up on the assert, in which case we can address the cases
proactively rather than waiting for valgrind to flag them.
Merge branch 'master' into fixMemcpyOverlap
Merge pull request #759 from hildeth/fixMemcpyOverlap

Fix memcpy overlap tail

Greg's suggested change did not work with CHPL_COMM=gasnet, so I backed it out.

Also, when building launcher code, chpl_memcpy is not defined, so I reverted the memcpy --> chpl_memcpy change as needed.
Unsuppress LeakedMemory5 for baseline testing

This also passes baseline testing now because of my change to the parallelism
debugging in DefaultRectangular.
Merge pull request #761 from lydia-duncan/unsuppressBaselineTest

Unsuppress LeakedMemory5 for baseline testing

This also passes baseline testing now because of my change to the parallelism
debugging in DefaultRectangular.
Quiet overflow test on cygwin and whiteboxes.
Merge pull request #762 from hildeth/quietOverflowTest

Quiet overflow test on cygwin and whiteboxes.