On 08/07/2014 14:50, Roman Gareev wrote:
You may want to take a look at polly commit r212186, where I reworked
and documented how this works.
It is much easier for understanding. Thank you! I've tried to consider
an older version.
Is this necessary? The id should already be set in
(graphite-s
>You may want to take a look at polly commit r212186, where I reworked
>and documented how this works.
It is much easier for understanding. Thank you! I've tried to consider
an older version.
>Is this necessary? The id should already be set in
>(graphite-sese-to-poly.c):
>
>static isl_id *
>isl_i
[Forgot to answer two questions]
On 07/07/2014 12:33, Roman Gareev wrote:
Hi Tobias,
I think that, according to the std::map feedback, we could use
std::map now and replace it with hash_map later, if its performance is
better.
Right.
> However, I propose to temporary postpone this and work o
On 07/07/2014 12:33, Roman Gareev wrote:
Hi Tobias,
I think that, according to the std::map feedback, we could use
std::map now and replace it with hash_map later, if its performance is
better. However, I propose to temporary postpone this and work on
gimple code generation from isl_ast_node_use
Hi Tobias,
I think that, according to the std::map feedback, we could use
std::map now and replace it with hash_map later, if its performance is
better. However, I propose to temporary postpone this and work on
gimple code generation from isl_ast_node_user, because we already have
generation of lo
