other approach for detecting and comparing loop
iterators for CLAST loops?
--
Alexey Kravets
kayr...@ispras.ru
* graphite-opencl.c: Use zero_dim_array_p instead of
graphite_artificial_array_p.
diff --git a/gcc/graphite-opencl.c b/gcc/graphite-opencl.c
index ea894ee..53704d2 100644
--- a/gcc/gra
ed by kernel launch).
--
Alexey Kravets
kayr...@ispras.ru
Also, we are currently working on another project (OpenCL implementation for FPGA), so
we can work on the graphite-opencl part-time only (mostly support and bugfixing).
--
Alexey Kravets
kayr...@ispras.ru
ARM C/C++ Compiler, 4.1 [Build 713]
The file has been compiled with following options:
for GCC:
-O3
for ARMCC:
-O3 -Otime
--
Alexey Kravets
mr.kayr...@gmail.com
.file "sort.i"
.global __divsi3
.text
.align 2
.global shell_sort
.type
and its callers;
> perhaps, the issue is that it fails to account for IVs created in inner loops
> when processing outer loops.
Thank you, I will check it.
>
> In any case, I recommend to create a bug report in the GCC bugzilla for this
> problem.
Yep, will do it.
>
> Hope t
Hello,
I am looking for a way to implement source annotation (or something
similar) for a for loops. Basically, I need some mechanism to mark
certain for loops in the source code for the GIMPLE optimization
passes (for C/C++ only currently).
For example something like this:
int i;
__attribute__((m
Hello,
That looks interesting thanks for pointing that out.
On Mon, Dec 3, 2012 at 5:11 PM, David Malcolm wrote:
> On Mon, 2012-12-03 at 12:19 +0100, Richard Biener wrote:
>> On Mon, Dec 3, 2012 at 11:05 AM, Alexey Kravets wrote:
>> > Hello,
>> > I am looking fo
