I am adding the baseline c version of the code
Including 2 different version of the the CFD-mini benchmark.
One is the baseline chapel
one is the baseline c
Last week I had started reworking my noinit tests now that _defaultOf is in the
repository.  This is just storing all those changes until I can get back to it
Number of edits:
1) re-renamed the 1D/2D situation.
   Names reflect the data dimensionality, and not the dimensionality of the tile.
2) Unified graphs by dimension. There is now only a Jacobi-1D and Jacobi-2D graphs.
Several things:
1) re-renamed files, from plain "Diamond-Tiling" to "Sliced-Diamond-Tiling"
   I figured that this will ease some headaches when we get regular, unsliced Diamond Tiling
2) Added the OpenMP C versions for 1- & 2-D, of Naive-Parallel and Sliced-Diamond-Tiling
Fix gmp build for 32bit ubuntu.

Need to set ABI=32 when calling ./configure.
Merge branch 'master' into betterNoinitTests
Remove .future files for usedWithSync and usedWithSingle.

A while back, we came to the consensus that syncs and singles should not support
noinit, so their behavior today is correct.
Update some more tests.

I need to task switch so I'm going to save what I've done today.
Attempting a merge

Merge remote-tracking branch 'upstream/master'

Conflicts:
	test/GRAPHFILES
Update cobegin-stacksize.

This test was originally added with the following message:

"Add a test that fails (on linux systems, anyway) unless the new callStackSize
config const is set at execution time, as it is in the .execopts file here."

However the failure mode really depends on the configuration (--baseline,
default, --fast) and exactly what code we're generating. Currently this tests
pases with default without setting CHPL_RT_CALL_STACK_SIZE so it's not really
testing what it intended to anymore (which I think is just that
CHPL_RT_CALL_STACK_SIZE actually changes the call stack size beyond just what
the tasking layer reports to us.)

To make it more portable to different configurations this updates so the test
runs in two modes. One with 32KB which will always fail, and one with 32MB
which should always pass.
iFixed the problem size
Update cobegin-stacksize execopts based on Greg's feedback

Don't need the B in MB/KB.

"The 'B' won't hurt anything (it'll be ignored), but having it there might
confuse people into thinking it was necessary/meaningful."
Update four more tests.

There's a lot that still need updating, but progress is good.
Snapshot based on this morning's returns (and late ones yesterday)
Don't use --fast in correctness testing, and don't use --no-cc-warnings at all
Add additional BigInt constructors for [u]int(64) args (where c_[u]long is expected).

A few tests in modules/standard/gmp were failing on linux32 to resolve calls
like "BigInt(bool, uint(64)" or "BigInt(int(64))". The intended constructors
were "BigInt(init2:bool, nbits:c_ulong)" and "BigInt(num:c_long)" respectively.

Create the [u]int(64) versions and cast from [u]int(64) to c_[u]long.
Also removing --no-cc-warnings for explicit/
Get rid of c_[u]long BigInt constructors.

On 64bit platforms, they confuse function resolution as [u]int(64) and c_[u]long literals are the same.
Merge pull request #806 from benharsh/minimd-fix-compopts

Clean up miniMD compopts

Remove "--fast" from correctness compopts, and remove "--no-cc-warnings" from both compopts.