Add the new release/1.10 branch dates to perf data files.
Never copy strings to remote locales unless passed by reference.

This commit fixes the unexpected behavior where strings are copied to
remote locales if the .locale field is accessed.  Long term the one
line fix in insertWideReferences.cpp will go away, but I wanted to use
this as an experiment to see how difficult it would be to use the
NewString module from an internal module.  The MemoryTracking module
abused the unexpected behavior of string, and so with this commit I
use the NewString type in MemoryTracking.

With this change, the only remaining instances of when we copy strings
to remote locales is when the string is passed by reference.  When the
new string implementation is made the default, this too should go away
(handled in codegen), and the runtime function
chpl_gen_comm_wide_string_get() should be removed.

This commit also changes some test output to include the NewString
module.  For test/multilocale/bradc/globalConstRepl.chpl, this
unexpected string behavior was masking an actual bug, so that test was
split into two.  The original test removed the string case (so as to
continue testing the rest), and the string case is now a future in
stringConstRepl.chpl.
Merge branch 'master' of github.com:chapel-lang/chapel into remove-remote-string-copy
Merge pull request #593 from sungeunchoi/remove-remote-string-copy

Remove remote string copy

[reviewed by Kyle]

This commit fixes the unexpected behavior where strings are copied to
remote locales if the .locale field is accessed. Long term the one
line fix in insertWideReferences.cpp will go away, but I wanted to use
this as an experiment to see how difficult it would be to use the
NewString module from an internal module. The MemoryTracking module
abused the unexpected behavior of string, and so with this commit I
use the NewString type in MemoryTracking.

With this change, the only remaining instances of when we copy strings
to remote locales is when the string is passed by reference. When the
new string implementation is made the default, this too should go away
(handled in codegen), and the runtime function
chpl_gen_comm_wide_string_get() should be removed.

This commit also changes some test output to include the NewString
module. For test/multilocale/bradc/globalConstRepl.chpl, this
unexpected string behavior was masking an actual bug, so that test was
split into two. The original test removed the string case (so as to
continue testing the rest), and the string case is now a future in
stringConstRepl.chpl.
Merge pull request #548 from thomasvandoren/update-perf-stuff-for-release-1.10

Add the new release/1.10 branch dates to perf data files.