[graphite] Backend fixes

Jack Howarth howarth@bromo.msbb.uc.edu
Mon Aug 25 14:28:00 GMT 2008


On Mon, Aug 25, 2008 at 05:58:22AM -0300, Tobias Grosser wrote:
> Hi,
> 
> Jan committed on Saturday some large parts for the code generation. Here
> the next fixes to hit some more bugs.
> 
> 
> Always generate graphite code.
> ==============================
> 

Tobias,
     The situation regarding code generation from graphite is still a bit confusing.
Sebastian left me with the impression that the bottleneck preventing the backend
from generating code from the new loop optimizations in graphite was the absence
of simplification operation in ppl. I also was given the impression that code
generation would work fine with cloog/graphite/polylib since it already had the
simplification operation. You proposed patch seems to indicate that graphite wasn't
really wired up to generate code in the back end at all yet. Is that a correct
reading of the situation? Also, is it correct to say that graphite's code generation
was always designed to be done by converting the GIMPLE to GRAPHITE representations,
processing these with ppl/cloog and reconverting the results back into GIMPLE for
final code generation?
                   Jack



More information about the Gcc-patches mailing list