Ran ispell on Task_Parallelism_and_Synchronization.tex
Preliminary version of special functions proposal.
First update.
Merge branch 'master' into specAddSpecialFunctions
Added tests of some compile-time computations.
Complete first draft of Special Functions chapter.
Add the new release/1.10 branch dates to perf data files.
Revert "Ran ispell on Task_Parallelism_and_Synchronization.tex"

This reverts commit 6d1353e44fd40ba510ba5e63761189552cffce24.

# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
# On branch specAddSpecialFunctions
# Your branch is up-to-date with 'origin/specAddSpecialFunctions'.
#
# Changes to be committed:
#	modified:   spec/Task_Parallelism_and_Synchronization.tex
#
# Untracked files:
#	commit.txt
#	commits.txt
#	compiler/resolution/functionResolution.cpp.thh
#	modules/internal/#ChapelStandard.chpl#
#	spec/proposals/constructors/2012/
#	spec/proposals/specialFunctions/spec.aux
#	spec/proposals/specialFunctions/spec.out
#	spec/proposals/specialFunctions/spec.pdf
#	test/io/ferguson/obj.slow/
#	test/modules/hilde/obj.inline/
#	test/modules/hilde/obj.no-inline/
#	test/types/records/hilde/typeBecomesValueArg.chpl
#	test/users/hilde/initVsAssign.chpl
#	third-party/qthread/qthread-1.10/autom4te.cache/
#
#
# It took 2.67 seconds to enumerate untracked files. 'status -uno'
# may speed it up, but you have to be careful not to forget to add
# new files yourself (see 'git help status').
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.
Merge pull request #592 from hildeth/specAddSpecialFunctions

A draft proposal for a new Special Functions chapter.



Initial draft. Feedback welcome.

I wanted to collect descriptions of compiler-generated functions in one place for easy reference, but some of this material is redundant with material already present in various places in the spec. So one way to integrate this with the spec would be to turn it into an appendix with cross-references, and then ensure that all of the important content was integrated (duplicated) in the body of the spec.
Clean up the include dependencies in bb.h and then compensate for the trivial fallout
Trivial formatting of some output
Add script for creating release tarball.
Merge pull request #597 from thomasvandoren/tarball-script

Add script for creating release tarball.

This adds a little structure around the process of creating a
release tarball.
Merge pull request #598 from noakesmichael/bb-cleanup

Trivial cleanup to support WhileDo stmt integration

I am trying to study possible issue(s) in BasicBlock code that is blocking integration of WhileDo stmt.

1) Cleaned up some unnecessary #includes in bb.h and then compensated downstream

2) Tweaked the output for AstDumpToNode to help in debugging


No functional changes in compiler behavior.

1) Compiled on Mac with clang  STD/LLVM
2) Ran start_test on release/

Same changes on a different branch was compiled on Linux/GNU and ran full regressions

No review.
Added a future for const checking of array-typed fields
Merge pull request #604 from vasslitvinov/add-const-checking-future

Added a future for const checking of array-typed fields.

From .future:

Const checking is not performed for an array field or a record.

An error needs to be reported either when it is a 'var' field of a 'const' record, or when it is a 'const' field of any record.

TODO: check 'const' field of a 'const' record.

TODO: check when it is a class, not a record.
NB accesses to 'var' array fields of a 'const' class-typed variable
are OK, as opposed to records.