Fixed spots in DefaultRectangularArr where 'low' should have been 'alignedLow'.

Also added bounds checking for the _ddata member of DefaultRectangularArr
(by storing the number of elements allocated into it).
All tests passed this checking (with COMM=none), so I commented it out
(because they probably would affect performance).
We might want to enable them, say, when running nightly valgrind testing.


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18573 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
More cleanup in top-level directory

1) Added data parallel hello, world with comments

2) Some wordsmithing on other .chpl comments

3) Moved to directory-level PREDIFF to clean up a bit

4) Removed feature tables from README.features

5) Added new test to Makefiles and READMEs



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18574 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
More updates to hello, world programs

1) Added distributed memory data parallel version

2) Renamed hello-multiloc to hello-taskpar-dist to unify

3) Replaced .numlocales files with NUMLOCALES





git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18575 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Took up the suggestion to number the hello tests

I can't remember who suggested it, but part of my
liberation in renaming these tests to names that
weren't forced to try and get alphabeticalization
came from deciding that I would number them in
order to help them be considered in a good order.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18576 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Adding the variants/ directory to hpcc/

Adding the variants/ directory we discussed to the hpcc/ directory
to capture more elegant (or sufficiently interesting) variants on
our official entries (which sometimes sacrifice elegance in order
to get better performance with today's compiler).

At this point, I added two variants, one for promoted stream, one
for RA using a much cleaner loop.

I inherited the .perf* files from the originals, but didn't copy
the .graph files, figuring we'd want to overlay the performances
together on a single graph.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18577 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Generate filenames in the spec for examples with test codes (to be
included in the release).  This required reworking the way test
programs are extracted from the spec.

- Added a new environment 'chapelexample' that requires a single
  filename argument.  This filename will appear in the spec as follows:
     Example (foo.chpl)

- Added a 'chapelnoprint' environment that will add the code to the
  test, but no print it in the spec.  This could subsume 'chapelpre'
  and 'chapelpost' if people were willing to write their examples "in
  program order".  I think most people already have done that.

- Updated documentation regarding generating tests in the spec.

- Updated the examples in the spec to use the 'chapelexample'
  environment.

- Give better statistics.  Currently, we have 241 uses of the 'chapel'
  or 'chapelcode' environment and 117 of them have been turned into
  tests.

- Change the directory names to match the filename minus the
  extension.

- Remove empty directories.

- Have 'make spectest' put the autogenerated tests in
  test/release/examples/spec.

NOTE: This change greatly simplified the extract_tests script since
all test programs are nested in a 'chapelexample' block.  It also made
it easier to have an example with multiple blocks of code.  Some of
these used to be 2 separate tests where code was repeated in the
second test, which is why there are slightly fewer tests with this new
scheme.

TODO:
- Handle _ in filenames a little better
- Auto generate the tests for nightly testing when only testing the
  release/examples directory
- Consider removing 'chapelpre' and 'chapelpost'



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18578 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Some wordsmithing and reformatting of main examples READMEs



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18579 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Added descriptions of the nanox and qthreads tasking layers

(in hopes that somebody might make sure they work for people other
than me tomorrow :).



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18580 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Being a bit more consistent in using the terms Nanos++/Qthreads

(vs. nanox/qthreads)




git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18581 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Minor wordsmithing and formatting changes



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18582 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Commenting out --regex flag that was added to etags in r18092 because it is not portable (to cygwin in particular) and is not important to an end-user of the release

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18583 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Oops -- hadn't realized that these tests specified .dat files explicitly

In copying the existing .perfkeys files last night, I hadn't noted that
they name their .dat files explicitly, and thus ran into the error
check when two performance tests name the same .dat file (thanks for that
check Sung!).  My bad.  This should fix the broken performance testing
from last night.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18584 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
A bit of noise but nothing too serious as far as the release goes...

* multirealm failed on GASNet -- I suspect I did something wrong in moving
  it but am not yet sure what; doesn't go into the release, so not critical
  (bradc)

* pvm timeouts: might be that Lee does a reset of PVM each day to clean up
  and that failure to do that caused more timeouts.  Or maybe his machine
  just misses him?

* x2-sim failure similar to an existing one (related to using serial
  iteration rather than leader/follower).

(not indicated here, performance failures due to duplicate .dat files;
 I just fixed)



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18585 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Oops, forgot closing parenthesis in my message due to fatigue last night

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18586 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Expanded the text in reductions.chpl to give a better explanation
of how reduction works.


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18587 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Pass the -hfp1 flag to the Cray compiler when Chapel's --no-ieee-float
flag is specified.

When using the Random module, -hfp2 (the default) produces numbers
that do not match the expected values, possibly producing
non-pseudorandom streams.  I have not yet figured out if this is a
problem with CCE.  It could also be assumptions we make about signed
integer overflow.

BTW, the craycc man page does not explicitly state that -hfp0 conforms
100% to the IEEE floating-point standard (as is implied by Chapel's
--ieee-float).

This fixes the following XT CCE regressions:

     [Error matching program output for performance/sungeun/assign]
     [Error matching program output for performance/sungeun/dgemm]




git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18588 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Added some simpler examples in front of minLoc, maxLoc.


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18589 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Add --no-futures flag that will omit futures from the generated tests.
Updated statistics to indicate how many futures were generated.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18590 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Have the gen_release script auto generate the tests from the spec
(minus futures) into the examples directory.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18591 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Removing redundant developer rule

When I moved this to third-party/Makefile, I forgot to remove it here.



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