Move while stmt from block stmt 2 keywords to other.

Make while an other keyword (c-other-kwds) in emacs major mode instead of block
stmt with 2 keywords (c-block-stmt-2-kwds). Before this change, the indentation
for the block of while loops that did not surround the conditional in
parenthesis was broken.
Replace <locale>.numCores with <locale>.maxTaskPar where appropriate.
Remove an extraneous space character.
Merge branch 'master' of github.com:chapel-lang/chapel into update-while-stmt-in-emacs-mode
Copy etc/emacs/23/chpl-mode.el to etc/emacs/.
Remove version specific chpl-mode.el files. They were identical.
Create symlinks for emacs/{22,23}/chpl-mode.el to preserve backwards compatibility.
Making tcmalloc the default when compatible with host compiler
Update etc/emacs/README with correct information.
rst-ify etc/emacs/REAME
Using target compiler instead of host compiler
Fix formatting of directory index.
Reference both .emacs and .emacs.d/init.el files.
Properly escape text snippets for monospaced font-ing.
Update tests that reference numCores to reflect maxTaskPar change.

A number of tests refer to <locale>.numCores.  Many do so in order to
parameterize parallelism.  Others do so in order to print information
about the testing environment.  Adjust all these to parameterize or also
print using maxTaskPar.
Fix a mis-coding.

I added new output lines for maxTaskPar in these tests, to go with the
existing ones for numCores, but I didn't put them under control of the
if-stmt that prevents printing them unless desired.  As a result, the
tests didn't match their .good files any more.  Fix that.
Simplifying logic
Build fewer LLVM components to speed compile

This patch significantly reduces the build
size and the build time. It omits some LLVM
and Clang components we don't use and only
builds host and x86 and x86-64 backends.

Used to take 23 minutes, now takes 18 minutes
to CHPL_LLVM=llvm time make on my machine. In
addition, llvm/build is now 8G (was 12G)
and llvm/install is now 4.6G (was 5.8G).
Split out the graphs for EP and FT that are most important to us (largest that run)
Significant refactoring (mostly expansion) of graphs in the perf tracking suite

I added a bunch of graphs to the perf tracking suite that I think we should be
paying attention to (and removed one):

* EP Stream -- I took the version that has --local and --no-local results
  though I think all our stream graphs should be condensed down to 1-4
  and don't understand the relationship between this graph and the release
  version (TODO)

* Removed Global stream w/ promotion -- because the global stream graph we
  use subsumes this info

* added HPCC RA and HPL : the first because it's important to us; the
  second because it's fairly stable and interesting; FFT could also have
  been added, but it seems less stable (and is arguably less "the way
  we'd like to do it"

* added thread-ring and pidigits -- the former is now less noisy with
  qthreads; the latter is now interesting with GMP on in the nightly
  testing

* added NAS EP B, FT A, and IS S -- all of these need more eyes on them
  to make sure they're as we like them; but in the meantime they're
  fairly noise-free

* added many array performance tests -- I looked for ones that looked
  fairly noise-free; I think that maintaining/improving performance for
  these is key, so thought they were worth a look

* dynamic iterator -- of the various advanced iters, I chose this one
  because it's the one we use most commonly and because it had some
  interesting changes lately.

* various scalar idiom C vs. Chapel comparisons -- again, these will
  be key to performance and they're fairly noise-free

* compilation time -- grabbed this just so we have some sense of
  overall compiler performance from week-to-week without bringing
  up Elliot's full suite -- this can serve as a canary to look there.

* memory leaks for examples -- this is something else I'd like to keep
  an eye on.  I could imagine taking one graph from this suite, but
  didn't put in the time to split the one I liked off (probably memory
  leaks for examples)

* jacobi AST/generated code size -- something else worth tracking

* no-op -- maybe not worth tracking, but I wanted to err on including
  it.