Throwing -Wno-inline for GASNet builds

Michael and Tom were correct and I was mistaken: It is GASNet's
"optimization" flags that are causing -Winline to be thrown.  The last
time I looked into whether we used GASNet's choices of flags, it seems
that I only looked in the runtime which is why I was mistaken: We
don't use GASNet flags for building our runtime, but we do for the
generated code.





git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@21985 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Further primping of threadring for the release

[reviewed by Lydia]

* changed the initial header to the prescribed format, including
  updating the URL and removing the description of the benchmark
  (and keeping your email addresses out of the hands of spam
  robots....).

* made comment formats more consistent with what most other
  release/examples/ do:
  - use blocks of single-line comments rather than multi-line
  - used initial and trailing blank // lines
  - aligned end-of-line comments on sibling declarations
  - moved comments before the things they are commenting on

* switched the domain to a range (lighter-weight) and gave it a
  descriptive name; changed index variable name in coforall to
  also suggest threads.

* decaptilaized 'N' for consistency with other shootouts and typical
  Chapel style for scalars (note that this also requires changes to
  .execopts...)     

* removed reference to other versions (seems like they might
  change over time.  Note that mimicking is spelled wrong if
  that comment were to stay in.

* got rid of underscores and renamed ring_link while there




git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@21986 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Added TODO to generated code's Makefile.include

While implementing the -Wno-inline issue, I noticed for the first time
that the compiler line we use to build a generated executable has
become pretty ridiculously long and redundant.  From what I can tell,
this is because at some point (I think mppf's 19641) we decided to add
all of the RUNTIME_CFLAGS to the GEN_CFLAGS variable which already had
many of the same shared sub-variables -- so, for example, all of the
warning flags now appear twice.  

I believe the better fix would be to tease the parts of RUNTIME_CFLAGS
that we think we need in both cases (and from the comments, it appears
to be -D flags to define tasking models and such) into its own
Makefile variable and then including this variable in both
RUNTIME_CFLAGS and GEN_CFLAGS rather than just having GEN_CFLAGS
include all of RUNTIME_CFLAGS (since they were architected to be
siblings, along with COMPILER_CFLAGS).

This was a bigger change than I could take on prior to the release,
and arguably just for aesthetics (or ability to make sense of the cc
line used to compile generated code) so I didn't.




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