You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to have a way to throw type-checking errors when certain accesses use non-constant values.
We want this for Affine-Indexing, and also for indexing into vectors and matrices. In the latter case, we want to be able to have loops over constant ranges generate indices with known bounds (i.e. not constant, but something we can certify is ok to index with statically.
Also, this issue may be related to #34 which handles a special form of constants: strings, which can't be manipulated with computation/arithmetic anyway.
The text was updated successfully, but these errors were encountered:
gilbo
changed the title
Simple "Constant Analysis" in Typechecker
Simple "Literal Analysis" in Typechecker
Jun 3, 2015
gilbo
added this to the
Legion single-core perf and Features milestone
Jun 3, 2015
We want to have a way to throw type-checking errors when certain accesses use non-constant values.
We want this for Affine-Indexing, and also for indexing into vectors and matrices. In the latter case, we want to be able to have loops over constant ranges generate indices with known bounds (i.e. not constant, but something we can certify is ok to index with statically.
Also, this issue may be related to #34 which handles a special form of constants: strings, which can't be manipulated with computation/arithmetic anyway.
The text was updated successfully, but these errors were encountered: