On 2012-06-12 11:26, Richard Sandiford wrote:
> Tejas Belagod writes:
>> New patch attached. OK?
>
>> +There are two standard integer attributes: @code{int}, the name of the
>> +code in lower case, and @code{INT}, the name of the code in upper case.
>
> I don't think this is true. So the surrou
Tejas Belagod writes:
> New patch attached. OK?
> +There are two standard integer attributes: @code{int}, the name of the
> +code in lower case, and @code{INT}, the name of the code in upper case.
I don't think this is true. So the surrounding paragraph reduces to:
It is possible to define a
Richard Sandiford wrote:
Thanks for the update.
Tejas Belagod writes:
+/* Implementations of the iterator_group callbacks for ints. */
+
+/* Since GCC does not construct a table of valid constants,
+ we have to accept any int as valid. No cross-checking can
+ be done. */
+
+static int
+
Thanks for the update.
Tejas Belagod writes:
> +/* Implementations of the iterator_group callbacks for ints. */
> +
> +/* Since GCC does not construct a table of valid constants,
> + we have to accept any int as valid. No cross-checking can
> + be done. */
> +
> +static int
> +find_int (co
Richard Sandiford wrote:
As discussed in the context of the AARCH64 submission, this patch
rewrites the iterator handling in read-rtl.c so that we record
iterator positions using an on-the-side VEC rather than placeholder
modes and codes. We then substitute in-place for each sequence of
iterator
As discussed in the context of the AARCH64 submission, this patch
rewrites the iterator handling in read-rtl.c so that we record
iterator positions using an on-the-side VEC rather than placeholder
modes and codes. We then substitute in-place for each sequence of
iterator values and take a deep cop
