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
I spent a few hours tonight taking a stab at writing an alternate
version of the cd-mini code, in part to get my head around what
it does (nothing like rewriting code to understand it).

The main changes I took on were:

* converted the 5D arrays to 1D of 1D of 3D arrays which seems to
  match its logical structure better (and similarly, the 4D arrays
  to a 1D of 3D).  This killed performance unless I also made either
  aliases to the inner arrays when I was computing on them for
  awhile or passed them into routines that chewed on them.

* also created routines in order to try and remove the amount of
  redundancy in the code.

I don't feel fully confident that I got everything correct, and
am worried that the correctness check is not tight enough that
it would necessarily catch problems if I did get something right.

It's also almost certain that my variable names could be made better
-- I didn't always know what they were representing, especially as I
was introducing formal argument names for the routines I was
injecting, and would be happy for suggestions for improvement.
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
iFixed the problem size
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)
I am removing the extra graph files
fixed the indexing bug found by Brad
Revert "Remove .future files for usedWithSync and usedWithSingle."

This reverts commit 2d6f5bf95a49b00d7d9b8a6248a7be25dc50403f.

Tom advised waiting to remove these futures until we'd had a group discussion on
the semantics of noinit for syncs and singles, so I'm reverting this change.
Rearrange the output to catch reversal cases.

If noinit were somehow using _defaultOf and the default case was skipping it
entirely, this test would not have caught that case.  Thanks, Tom, for pointing
it out!
Merge pull request #809 from lydia-duncan/betterNoinitTests

Clean up/strengthen the noinit tests [reviewed by hilde]

Previously, the noinit tests had relied on accurate
later assignment and a hacky grep of the generated
code (in the case of enums as it was simpliest) to
assure us that default initialization had been properly
skipped. Brad had suggested way back when that we
would be able to better test if noinit had actually worked
by using the _defaultOf functionality - by redefining the
default behavior to include displaying a message
whenever it was invoked, the absence of this
message would indicate when the default behavior
did not occur. Now that _defaultOf is in the language,
I have replaced/updated some of the tests in this
directory to use this improved method of determination.
Resolve baseline future

My commit yesterday to fix --no-remove-copy-calls/initCopy with extern structs
resolved this future.  Since the future was a copy of
test/extern/bradc/structs/externFloat4calls.someFields.chpl, I am removing the
future in its entirety and allowing the someFields test to run with --baseline
again.
Merge pull request #815 from lydia-duncan/resolveBaselineFuture

Resolve baseline future

My commit yesterday to fix --no-remove-copy-calls/initCopy with extern structs
resolved this future. Since the future was a copy of
test/extern/bradc/structs/externFloat4calls.someFields.chpl, I am removing the
future in its entirety and allowing the someFields test to run with --baseline
again.