Adding a future for chpldoc specified comments.

Sung exposed a bug by having a comment which started with the specified header
of chpldoc/compflags/comment/basic.chpl and loseComments.chpl but did not close
in the same style.  This led to a valgrind error because it was assumed that
these comments would match.  We believe the proper behavior is to drop such
comments when discovered, but warn the user that we are doing so.  However, this
is a low priority bug at the moment.



git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23624 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Setup default for execoptslist outside of testing loop
to ensure execution output log file names are correct.

Ran full suite of tests.

paired w/ eronaghan

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23625 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Split boolean immediate into different sizes [reviewed by Mike]

Previously, the boolean immediate did not vary depending on its size.  This
meant that for my default initialization work, the boolean size was lost when
casting from a literal to the desired type.  With this patch, the tests that
failed due to this bug will now pass.  Additionally,
types/tuple/bradc/unaryTupleOps.chpl needed to update its output to reflect our
differentiation between the different boolean sizes.

Summary of changes divided by change rather than file (with affected files as
header), except where changes are not trivial.  Thus, a single file will be
listed multiple times.

compiler/AST/expr.cpp
compiler/AST/stmt.cpp
compiler/AST/symbol.cpp
compiler/AST/type.cpp
compiler/ifa/num.h
compiler/resolution/functionResolution.cpp
compiler/resolution/generics.cpp
  Uses NUM_KIND_BOOL to determine if the immediate is a boolean, rather than
  depending on it being a uint or int of size 1.

compiler/AST/stmt.cpp
compiler/resolution/generics.cpp
  Uses method bool_value() to determine the value, rather than relying on there
  being a single field for booleans.

compiler/AST/symbol.cpp
  Update codegen for immediates to adjust for llvm.  Adjusted boolean symbol
  creation to assign the value to the appropriate slot depending on the size
  provided.

compiler/AST/type.cpp
  Adjusted INIT_PRIM_BOOL to match the formatting of the other INIT_PRIM_*s
  (pretty trivial)

compiler/ifa/cast_code.cpp
compiler/ifa/num.cpp
  Added case for booleans, and removed the INT_SIZE_1 case as it was only used
  for booleans.

compiler/ifa/num.h
  Added NUM_KIND_BOOL to IF1_num_kind. Made the slot in class Immediate store
  a uint instead for differently sized booleans.  Added a method for
  determining the boolean value stored in the immediate.

compiler/passes/normalize.cpp
  Since there is no more INT_SIZE_1, start the loop over INT_SIZE_* with the
  new lowest, INT_SIZE_8.

test/types/tuple/bradc/unaryTupleOps.good
  Reflects that we now distinguish between booleans of different sizes within
  the compiler (although we do not yet generate booleans of different sizes).



tested over std/
            llvm/ (extern/, release/examples/)


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23626 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Updating the message for this future.

My boolean immediates change has put the compiler in a better position for this
change, but there is still work needed.  Updating the message to reflect what
path I think would resolve this bug.



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