Tightened up the definition of the div and mod operators, to match the behavior
demonstrated by test/expressions/hilde/divByNeg.chpl.


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18769 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Lower maxThreadPerLocale for stress.chpl.

Lower maxThreadPerLocale to 250 (below the GASNet limit).



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18770 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Revised MultiDomain structure.  Deleted advection/static_mr directory.  Handful of other maintenance fixes.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18773 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Changed the interface for the comm diagnostics and brought all comm
layers up to the current communication interface.

- Changed the type returned by getCommDiagnostics() to a record called
  commDiagnostics (rather than a homogenous tuple) to make it easier
  to use and maintain
- Added resetCommDiagnostics() and resetCommDiagnosticsHere()
- Added a struct in chpl-comm.h that defines which diagnostic counters
  are to be supported by every comm layer
- Prepped the runtime for exporting this struct to the module code
  (pending bug fix for extern types)
- Brought the comm layers up to the newest interface (including
  non-blocking get routines)

NOTE: The new record type (commDiagnostics) should eventually be the
same as the extern struct that I have defined in chpl-comm.h, but
currently we have no way to define the default values for extern type
and cannot properly support this.  Once this happens, we can remove
all the individual diagnostic functions (e.g., chpl_numCommGets(),
chpl_numCommPuts(), etc.) and use chpl_getCommDiagnosticsHere() to
fill in the struct.

doc/release/technotes/README.comm-diagnostics:
  Update for current interface.

runtime/include/chpl-comm.h:
  Added a struct called chpl_commDiagnostics that describes the
  diagnostic counters and their types.  Comm layers can chose to use
  this struct to store diagnostic data.

  Added chpl_resetCommDiagnosticsHere() to reset the counters on the
  current locale.

  Addded chpl_getCommDiagnosticsHere() which fills in the argument of
  type chpl_commDiagnostics with the current values (not currently
  used in ChapelLocale.chpl due to extern record issue).

runtime/src/comm/*/comm-*.c:

  Updated all the comm layers to the new interface.  Some do not
  implement comm diagnostics, so simply added stub routines.  All
  compiled and ran except ARMCI (for which I couldn't get the build
  working again -- not specific to this change).

modules/internal/ChapelLocale.chpl:

  Added a record with all the counters for the various comm types
  currently supported.  The function getCommDiagnostics() now returns
  a record of this type.  Added 2 new functions resetCommDiagnostics()
  and resetCommDiagnosticsHere() that zero all the counters on all
  locales or "here."

TEST UPDATES:

  Updated output to reflect new record interface.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18774 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Updating REGRESSIONS based on last 1-1/2 weeks runs

- new unreachable line warnings in generated range code (cray compilers)
  (Vass?)

- alignment of types/range/hilde/align prints out incorrectly on intel
  starting 04/25/11 (Tom?)

- some lingering assoc/stress regressions that will probably be fixed
  when the weekend runs go again (Sung)

* lots of compilation/execution timeouts; bumping up a handful of timeout
  files would probably go a long way



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18775 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Reset line numbers before inserting AST nodes during scalar replacement.

I made a vow to myself to fix such issues everytime I ran into them,
since I now know how to fix them.

When creating new AST nodes for scalar replacement, set the source
code line number used to that of the symbol that is being replaced.
This line number can show up in error messages and other parts of the
generated code.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18776 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Updating nightly to pass -comp-only rather than -componly to start_test

Also updating documentation and help message in start_test to reflect
-comp-only name.  This should fix the XMT testing failures from the
past few nights.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18777 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Updating REGRESSIONS based on weekend runs

- assoc/stress fails on --no-local due to warning about being unable to create
  > 1000+ threads; fails on valgrind due to "the impossible has happened"
  warning (also usually due to creating too many threads)  (Sung)

- 90-some unreachable loop warnings for Cray compiler due to existing problem
  (Vass)

- new tests compiling for XMT hardware (rather than simulator) reveal an
  assertion failure in release/examples/primers/arrays.chpl as Sung noted
  last week

+ otherwise assoc/stress tests generally doing better

* nondet. timeouts



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18778 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Bumping up timeouts for some of our serial nondeterministic failures...




git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18779 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Renamed dsiIndexLocale to dsiIndexToLocale
to match the forthcoming CUG 11 paper on DSI.

Only modules and README.dsi contained that name
(i.e. no other docs and no tests).

Files: modules; doc/release/technotes/README.dsi


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18781 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Fix range regression on xt-cle.

This differences arises because the integer rollover behavior is different on
this platform.  The test itself uses (maxS + 1) -- the maximum representable
signed integer plus one.  This quantity is machine-dependent, because it varies
with integer representation and rollover behavior.  So a machine-dependent .good
file is appropriate.


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18782 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Updating REGRESSIONS based on past few days' work

* reoccurrence of nondet. race on stdout for primers/taskParallel

* other standard nondeterministic timeouts



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18783 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Bumping TIMEOUTS for John's Cholesky tests

These are currently the most likely tests to time out nondeterministically.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18784 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Adding a README that Jim Dinan sent us for his UTS work...

Only 4 years later, not bad...  Maybe we'll hear from Jacob yet!  :)



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18785 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Workaround for bug in param conditionals in new (stridable-aware) indexOrder impl.

In indexOrder(), provides an else clause, so that there is an execution path in
the param if.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18786 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Fixed a typo in start_test.


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18787 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Turned the failing case in align.chpl into its own test (align64).

M    hilde/align.chpl
M    hilde/align.good
D    hilde/align.xt-cle.good
Removed the failing test case, making is possible to eliminate the platform-specific .good file.

A    hilde/align64.good
A    hilde/align64.chpl
A    hilde/align64.future
Added the failing case as a future (bug).



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18788 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Added test cases for duplicate auto destroys.

These are obtained by a reduction of a version of KM's graph500 code.
The common tune is an array of records, with each element
explicitly initialized via an assignment from a 'new' on the record type.

array-of-records-crash-1.chpl and array-of-records-crash-2.chpl
crash upon triplicate TILDA on a sync variable.

array-of-records-crash-3.chpl crashes upon a duplicate TILDA
on a domain.

Interestingly, uncommenting the explicit type of the array in the tests
eliminates the symptoms. (I have not investigated this.)


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18789 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Added a version of Kristi Maschhoff's Graph500 code
provided to us at the end of March '2011.

This code is based on the XMT version of the Graph5000 benchmark submitted by
John Feo <john.feo@pnl.gov> and Kristi Maschhoff <kristyn@cray.com> in 2010.

NUMLOCALES=4 was chosen arbitrarily.

Changes from Kristi's version:

* smaller problem size: SCALE 8->6, EDGEFACTOR 16->8

* output_result() simply prints "done"
  vs. calling an external function

---

NOTE: This program crashes under GASNet with
  *** Caught a fatal signal: SIGSEGV(11) on node XX/YY

Therefore I am adding it to REGRESSIONS right away.

The crash is intermittent, but I often get it when running the program
right after compilation.

For the record, when running with GASNET_BACKTRACE=1,
the thread that catches SIGSEGV has the following at the bottom of the stack:

#22 0x00000000006bc483 in gasnet_barrier_wait (id=0, flags=1) at /users/vass/chapel/third-party/gasnet/GASNet-1.14.2/extended-ref/gasnet_extended_refbarrier.c:1279
#23 0x0000000000690800 in chpl_comm_barrier (msg=0x8450b9 "chpl_comm_exit_all") at comm-gasnet.c:394
#24 0x000000000066e5fd in chpl_exit_common (status=0, all=1) at chplexit.c:20
#25 0x000000000066e647 in chpl_exit_all (status=0) at chplexit.c:34
#26 0x000000000066a071 in main (argc=3, argv=0x7fff411f5d68) at main.c:104


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@18790 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Preparing to check in a new version of Kristi's graph500 code as graph500/v2.

The current commit is a straight copy of graph500/v1,
to serve as a reference point for version comparisons.


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