Test cleanup: Serial true

With the 'serial do' => 'serial true do' addition earlier this
week, a number of tests can be cleaned up to use the new
shorter form.  This commit does just that.



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22617 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Change the IntentTag enum to support comparison like flags

This patch changes the numbering of the enum elements in IntentTag to support
binary operations for comparison. The main reason is to have a shorthand for
checking ref/const.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22618 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Update for triage handoff:
- The svn update for valgrind failed on the morning of 2/1, as it did on
  the previous valgrind the Saturday before.  Thomas is going to look
  into this.
- r22618 broke 7 tests; Kyle is looking.
- Remove the entry about log churn due to test script changes, as that
  seems to have all settled out now.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22619 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Adding a performance future for coforalls over the locales array. [reviewed by Sung]

As discovered in BlockDist.chpl, iterating over the locales array in this manner
ends up creating a task per locale, as it should.  Our performance would improve
if in this case a task was not created for the originating locale, as it will be
able to just pick up the creating task for its purposes.



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22620 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Fix intentDescrString not working correctly after r22618

[Reviewed by bradc]

intentDescrString was returning the name of the intent by directly indexing
into an array of names with the enum value. Since the intents were changed to
support comparison like flags in r22618, the values are no longer consecutive.
The proper string is now chosen via a switch statement.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22621 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Adding small README to the Distribution Robustness Suite directory

I was realizing that newer folks don't really know what this is, so I
added a small README.



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22622 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chap15 from all-cf.

git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22623 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Un-futurized the test users/vass/crash6defPointNotInAST.chpl.

It stopped failing on 9/13/2013. Given that the tests did not run
the night before it seems, the most likely suspect is r21849.

The reason we had not noticed that - and that it had been succeeding
under --baseline all along - is an incorrect .good, which I am fixing
as well.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22624 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Tidy up the future users/vass/internal-error-message.chpl.

Improved the desired error message; adjusted .future to have
a 1-line, not 2-line, description; updated .future contents
to the current error; added .bad.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22625 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Tidy up the future users/vass/div-ceil-on-more-int-types.chpl.

* Renamed ceil() to divceil(), correspondingly to what we have in Math.chpl.

* Added parallel tests for divfloor().

* Adjusted .good - explicit bitwidths for int types; ceil(7/5)=2 (duh).

* Added .bad.

* Renamed to remove "-1" in the test name.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22626 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Tidy up the future users/vass/crash1callDestructorsMain.chpl.

The original crash got masked most likely by r21105. Luckily,
a simple mod to .chpl seems to have restored that crash.

While here, I am adding a .bad and also a .prediff
to filter out the compiler file's line number and compiler version.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22627 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Removed the test users/vass/iterator-cpp-assertion-crash.chpl.

The original crash got masked at some point - could have been
similar to crash1callDestructorsMain.chpl - see r22627.
Applying that same trick here, however, did not bring that crash back.

As of r20660, iterator-cpp-assertion-crash.chpl is believed to expose
the same problem as crash4replLclsWFlds.chpl.

Given that crash4replLclsWFlds:
* is still around and kicking that problem, and
* is beefier than iterator-cpp-assertion-crash,
I do not see a need to keep iterator-cpp-assertion-crash around.

And, I am too lazy to figure out whether iterator-cpp-assertion-crash's output
needs to be sorted for determinism, whether I need to pass
--dataParTasksPerLocale=2, etc.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22628 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Add .bad for users/vass/crash4replLclsWFlds.

Also added .prediff to filter out error line number and compiler version.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22629 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Add .bad for users/vass/crash5insertAfter.chpl.

Also added .prediff to filter out error line number and compiler version.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22630 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Add .bad for users/vass/tuple-crash-1.chpl and dont-eval-dot-type.bad.

Also added .prediff to filter out error line number and compiler version.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22631 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Move the call to insertReferenceTemps() as late as it can go in the translation. [reviewed by kbrady]

Split the insertReferenceTemps() function into two.  The expansion of
INIT_FIELDS primitives was blended in with the original.
insertReferenceTemps() was moved from functionResolution.cpp to
callDestructors.cpp, and the call to it was placed at the end of the main
function for the callDestructors pass.

It is undesirable to insert reference temps early in translation, because the
inserted ADDR_OF primitives may have to be handled specially in subsequent
passes.  The immediate motivation for moving insertReferenceTemps() to the end
of callDestructors() is that the special case of ADDR_OF comes up in the
implementation of returnRecordsByReferenceArguments(), which is called earlier
in the callDestructors pass.  Moving insertReferenceTemps() after that call
obviates the special handling.

In might be possible to push the call to insertReferenceTemps() into the next
pass (lowerIterators), but it would have to appear early in that pass.
lowerIterators calls localCopyPropagation(), and copy propagation relies on the
reference temps having been inserted into the AST.  Also, insertReferencTemps()
is somewhat related to insertYieldTemps() which also appears in the
callDestructors pass.  So callDestructors seems like a better place for it.

[tested on / (std)]


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22632 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Clean up of distribution robustness suite

[approved by David]

- Removed arithmetic/driver*.good files as they are no longer needed.
  The driver files used to have .noexec files, but we replaced them
  with .notest at some point and never removed the .good files.

- Move all the tests in the arithmetic/performance down a level to a
  directory called 'multilocale', as they require multilocale
  execution.



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22633 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
We cannot assure that task reporting will be deterministic in multilocale
settings, so skip these four tests if CHPL_COMM != none
[reviewed via chat by gbt]



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22634 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Fix bash syntax error in gasnet everything test.

It has not run for a while because of the >&! redirect.

git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22635 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Fix bash syntax error in bradc-lnx crontab.

git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22636 3a8e244f-b0f2-452b-bcba-4c88e055c3ca