On Wed, Jun 29, 2011 at 10:35 AM, Sebastian Pop wrote:
> 2011-06-29 Sebastian Pop
>
> * graphite-clast-to-gimple.c (precision_for_value): Removed.
> (precision_for_interval): Removed.
> (gcc_type_for_interval): Use mpz_sizeinbase.
> ---
This caused:
http://gcc.gnu.org/bug
On 06/30/2011 09:50 AM, Sebastian Pop wrote:
On Wed, Jun 29, 2011 at 18:16, Tobias Grosser wrote:
why do we continue to call low 'low' and up 'up', if we actually just have
two values v1 and v2 where we do not know which one is larger? I think this
wrong and probably comes because we pass the l
On Wed, Jun 29, 2011 at 18:16, Tobias Grosser wrote:
> why do we continue to call low 'low' and up 'up', if we actually just have
> two values v1 and v2 where we do not know which one is larger? I think this
> wrong and probably comes because we pass the lower loop bound to val_one and
> the upper
On 06/29/2011 12:35 PM, Sebastian Pop wrote:
2011-06-29 Sebastian Pop
* graphite-clast-to-gimple.c (precision_for_value): Removed.
(precision_for_interval): Removed.
(gcc_type_for_interval): Use mpz_sizeinbase.
-/* Return a type that could represent the integer value VAL
