Wording fixes



See merge request !34

Tight (non-static) sequential loop bounds



See merge request !33

defined within a subkernel.

Introduce a check for writes to predicate variables (and prevent those) (Fixes #57 on Github)



See merge request !31

non-static loop bounds.

This is intended to help the case when one loop's bounds depend on
another loop, such as the domain

{ [i,j]: 0 <= i <= n and i <= j <= i }

In this case we want the generated code to look like

    for (i = 1; i <= n; ++i)
        for (j = i; j <= i; ++i)
            ...

rather than "for (j = 1; j <= n; ++j)" which are the static loop
bounds for j.

Additional changes that help realize this are as follows:

* Enable code generation of piecewise affine loop bounds, so that
piecewise affine constraints on the "j" loop may be expressed as
conditional expressions.

* Additionally, if "i" is marked local-parallel, we allow the "j" loop
bounds to depend on "i" as long as there are no barriers inside the
"j" loop.

Minor fix for global temporary declarations in C-based targets

make the device_decl_extractor a part of the Target class, which is not implemented except for c-based languaged