Removed a stray executable bit on gmp-5.0.1.tar


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22480 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Mandelbrot versions outputting to stdout without locking or using putchar.



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22481 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Adding Michael's putchar mandelbrot version to the graph file for nightly comparison.



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22482 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Pass CFLAGS along to configure step of hwloc and qthreads

[reviewed by Greg]

This patch passes CFLAGS/CXXFLAGS to the configure step of hwloc and
qthreads.  Couple of caveats:

- For CXXFLAGS I passed CFLAGS during the configure step, because we
  don't seem to use CXXFLAGS in a consistent manner throughout our
  build process.  We seem to add CFLAGS to other C++ compiler options
  when building, for example, the compiler.

- The qthreads tasking layer is implemented in the third-party
  directory, so if you want optimizations turned on, you must
  explicitly set OPTIMIZE=1.



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22483 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Tests for proposed improvements to C integration.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22484 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Bug report showing problem with record reading.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22485 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Bug report showing problem turning string back into record.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22486 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Bug reports for various non-default literals


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22487 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Shows the problem with + reduce on strings


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22488 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Test checking that the on A[i], when it's nil, still works right.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22489 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Test showing problem with passing tuple to extern fn.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22490 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Bug reporting showing return from a local block.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22491 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Don't run single-thread fifo tests on > 1 locale, because they always fail.

[Not reviewed.]

The tests QueuedTasks, OneThread, and OneThreadSyncStmt were all written
specifically to test single-thread behavior with tasks=fifo (which used
to be called tasks=pthreads).  They can't work properly in multilocale
execution with tasks=fifo nowadays, because the r22232 optimized locales
initialization using coforall+on needs multiple tasks per locale and we
can't run multiple tasks per thread with fifo.  Therefore, turn these
tests off for CHPL_COMM!=none.  They still fulfill their original
intent, which was to test the fifo tasking layer, but only on a single
locale.

To offset this restrictiopn, for OneThreadSyncStmt, rather than skipping
when tasks!=fifo, skip when tasks=none.  That test does work for all the
tasking implementations other than none, so there's no reason not to
test it for all of them.  This is especially true when for example the
major benefit of qthreads is user task switching on threads, or at least
shepherds; we might as well test that.

While here, I also added a skipif for tasks==none for OneThread.  It
didn't use to have one even though it was originally written to test
tasks=fifo just like OneThreadSyncStmt was.  It doesn't work with
tasks==none any better than the others do.

I didn't change the CHPL_TASKS!=fifo skipif for QueuedTasks.  It will
potentially produce different output for each tasking implementation,
and I didn't want to go to the trouble of figuring out all the cases at
this time.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22492 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Adding bug: to futures missing it


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22493 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Bug report showing wrong error with record = string


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22494 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Update comm counts due to r22438.

Revision 22438 added autoCopy and autoDestroy calls for user-defined record
types (passed by value) and internally reference-counted types, for data items
shared across a nonblocking "on".  

The autoCopy calls are necessary, to ensure that shared data is not released
prematurely by the spawning task.  The autoDestroy calls are then necessary to
release the shared data when the spawned routine is done.  (This manipulation
of reference counts was already in place for "begin" blocks; r22438 merely
expanded it to include nonblocking "on" blocks as well.)

This patch contains updates to the communication counts resulting from the
change.  Verbose logging was used to trace the changed comm counts directly
back to the changes introduced in r22438.  The changes are expected and easily
explained in terms of the added autoCopy and autoDestroy calls, as detailed
below.

DETAILS

    test/modules/sungeun/init/printInitCommCounts.good
One more fork is executed on each remote locale.  The extra remote call is due
to the inserted autoDestroy, which releases the "flags" array used to
synchronize initialization of the Locales array in initOnLocales().  The added
autoCopy calls, used to retain the "flags" array for the sake of each remote
locale do not add any communication, because the calls and the "flags" array
are all local to the root locale.

    test/studies/ssca2/performance/SSCA2_commDiags.good
The fork count on each remote locale increased by 1, and the get count
increased by 2.

The extra forks are due to inserted autodestroys for two shared variables:
_coforallCount and _formal_tmp_heavy_edge_list.  Only one of these generates a
fork, because the first variable is an integer and therefore its autoDestroy is
trivial.  

The extra gets are because the variables are read before being destroyed.
These reads can probably be removed as an optimization.  The wide access
inserts a read because the argument to autoDestroy is passed by value.  If its
intent was ref instead, the extra gets would go away.

    test/studies/hpcc/CommDiags/stream-ep_commDiags.good
The fork count increased by 2 on each remote locale.  Both are due to
autoDestroy calls added by r22438.

    test/performance/hilde/coforallOnByRef.chpl
    test/performance/hilde/coforallOnByRef.numlocales
    test/performance/hilde/coforallOnByRef.bad
    test/performance/hilde/coforallOnByRef.good
    test/performance/hilde/coforallOnByRef.future
Added a future to capture Vass's suggestion that extra comm counts can be
eliminated for the special case of a noblocking "on" inside a coforall.

    test/performance/hilde/userSync.chpl
    test/performance/hilde/userSync.numlocales
    test/performance/hilde/userSync.bad
    test/performance/hilde/userSync.good
    test/performance/hilde/userSync.future
Added a future to capture the fact that the "no copy" and "no auto destroy"
flags are not propagated through temp variables.



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22495 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Bug fix for compile error in reading record, and comment change.

Trivial and not reviewed. The regexp-handling code was assuming
that arbitrary (possibly user types, records or classes) could be
cast from a string in order to process capture groups. We now only
convert capture groups to primitive types.



git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22496 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Add new compiler options --explain-call-id and --explain-verbose.

--explain-verbose is a user option that turns on the disambiguation trace for
the selected function (using --explain-call) or instantiation (using
--explain-instantiation).  

--explain-call-id is a developer option that selects a call to explain using
the call ID.

To get the trace output to be properly interleaved, I changed the
TRACE_DISAMBIGUATE_BY_MATCH(...) macro to write its output to stderr (like
the output from --explain-call, etc.)

TODO: In this patch disambiguation tracing is always enabled at compile time.
We need to review compilation times, and see if this is acceptable.




git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22497 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Add two new versions of fasta: fasta-lines and fasta-printf

fasta-lines builds up a string for each full line of output within the
randomMake procedure, rather than writing each character out one by one. The
string concatenation causes a very large amount of memory to be allocated and
leaked, but it is still faster than fasta.

fasta-printf performs some trickery to use arrays as character buffers and
hands it straight to printf, bypassing qio. It is just meant to show the
overhead we currently have with string manipulation and qio routines.


git-svn-id: svn+ssh://svn.code.sf.net/p/chapel/code/trunk@22498 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Bugfix for compile error in MassiveThreads tasking layer.

This commit replaces c_sublocid_any by c_sublocid_any_val in
tasks-massivethreads.c in order to follow the change of their definitions.


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