Adding an example of providing one's own Locales array

This seems to be a frequently asked question, so I've added
an example of providing one's own targetLocales array to
our distribution primer for the release.




git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18905 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Initial commit of the PARACR algorithm for tridiagonal problems

Two versions: 
 1.- PARACR-B (Block distribution)
 2.- PARACR-BC (Block to cyclic redistribution)

BC version is faster. Performance files only for that version



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18906 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Removing .graph file that I missed in r18882.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18907 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Added some description of the compiler --runtime flag and fRuntime variable,
from Brad's email of 23 Jun 2011 15:56:47 -0500.


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18908 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Committinng a future showing the bug reported by Jens

In an email this morning entitled:

   [Chapel-bugs] error: internal failure CUL0097 chpl Version 1.3.0



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18909 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Fix bug in edge_weight iterator for the RMAT graph and increase
confidence when testing.

Fixed a bug in the edge_weight iterator for the RMAT graph where I was
iterating over the domain and not the weights themselves.  Since we
don't test with filtering on, and have limited debug output, I didn't
notice during my testing.

That motivated me to have more verbose output during testing (with
start_test):

- Turned on debugging output for all phases (graph generation, weight
  generation, kernel 2, kernel 3, and kernel 4).

- Add a prediff script for the output, because the order of the debug
  statements is non-deterministic due to parallel iteration.  I opted
  for a slightly more complicated prediff script than just sorting the
  output since we are running 4 graph versions and it is highly like
  that we could get false positive results if just sorting.  The down
  side of this is that we will need to modify it if we change the
  format of the output.

- Removed verbose comm calls when debug output is enabled for kernel 4.

- Update .good file

- Build torus versions for the SSCA2_main_atomic.chpl.





git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18910 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Added a .numlocales file for GASNet testing (currently set at 2 cuz 4
takes a long time the way we run the nightly).



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18911 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Committing the HPL mods that Vass and I started playing with this week



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18913 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Fixing bug pointed out by Jens Breitbart

Jens sent in a program that ran into an internal error due to
declaring a var function that did not return anything.  I
inserted a compiler semantic check error against this case
and also improved the internal error to print the location
of the call that caused the error to help provide some clue
as to where it's going (if others run into it along some
other path down the road).

Moved the future that I originally filed against this into
a subdirectory where it fits better and added a second
case (a return with no expression being returned) that
caused similar problems.

Had to update a few tests that had this behavior in code
that wasn't called or code that was testing compilerError
behavior.  In one case, I just made the function non-var;
in the other, I made the function return something to
preserve the original behavior that it was testing.




git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18914 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Adding a new primer to the release on leader/follower iterators

In working up an answer to Jens' email about leader/follower iterators
today, I decided that a primer on this topic would be in order, and
also would serve as a good ramp-up for the leader/follower iterator
paper I'm hoping to write for PGAS in the next few weeks.  I pulled
the leader/follower content from iterators.chpl and put a reference to
this new test instead.  Comments/feedback appreciated!



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18915 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Adding a bug future where the compiler crashes with an assertion (iterator.cpp:120).
This came up in my work on dimensional; I did not try to trim it down to a smaller test.
May be a repeat of another future.


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18916 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Fixed bug in prediff script that will make the output a little more
meaning up.  Updated the .good file to match.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18917 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Initial check in for 1D array representation for RMAT graph, changes to
RMAT graph generation, and Kernel 4 optimization using Chilren arrays 


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18918 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Fixed and simplified parsing of strings, aka eatStringLiteral().

With these changes:
* A backslash escapes only a single following character.
* If there is a newline character within a string, the line number counter
  is still incremented.

Removed the outermost 'while(1)' loop, which appears to be useful
but no longer is.

Extended Tom's 'escapes.chpl' test (with permission);
removed .future on it and on another test, as they now pass.

Added some very simple tests for eatStringLiteral()
(they intentionally generate compiler errors).


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18919 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Change level sets to be associative arrays.

Changed the level sets to be associative arrays rather than sparse so
that we could remove the explicit locking from the kernel 4 code.
This also required that we change the local sum for validation into a
sync since it is no longer protected by the lock.  We do not enable
validation when timing so it should not affect the performance
results.

Kristi and I agreed to do this for now to clean up the kernel 4 code,
though there may be a time in the future when we change this to
something else (possibly 1-d array).

It will be interesting to see if there are performance implications.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18920 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Implemented distributed level set work queues.

- Replaced the single level set work queues with a replicated version
  (one for each locale) that will only contain vertices that are on
  the current locale.

- Added "on" statement blocks to direct computation to close to where
  most of the data is.

- Changed the level set domain to associative as in the base version.

- Removed the comm diags from analyze rmat as in the base version.

NOTE: This does not get the correct answer for the Torus graphs when
using multiple locales.  I have not investigated this at all.  It does
get the correct answer for the RMAT graph (including debug output).

TODO:

- Multi-locale for the torus cases
- Remove redundant reduction for the termination condition




git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18922 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Added a reference to the leaderfollower primer to README.dsi.


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18923 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Fixed small type-o found by Rafa.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18925 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Fixed similar type-os found by Rafa (I should have waited until he
finished reading the chapter :).



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18926 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Some minor changes to make this test work properly

1) Added a #define to try and increase the odds that we get a C
   prototype of strdup().  This was required on my desktop to
   make it work in --local compilation

2) Added --no-local to the compopts file to make it fail every time
   rather than only when testing under GASNet.  This should remove
   the false positive of this being a passing future.




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