search for: clast

...xisting back-end to an adaptive and modular back-end which will unleash the power of Polly to other projects. To be short, I plan to implement my proposal in steps as follows: 1. refactor the existing back-end to a preliminary modular back-end. 2. Add A CodeGen adapter, abstract away the detail of CLAst. 3. Implementation of Specific code generation class to the new back-end. In this phase, I am going to implement a SIMD code generation class. An ultimate construction of the new backend will be like the figure below: [Original Polly codegeneration pass] [Click codegeneration[1]] [whole functi...

...problems and that you have an idea of how to approach them. In case you are unsure about something, it is better to say this and give a plan how you will proceed to find a solution than to propose a solution you are not yet sure about) > 2. Add A CodeGen adapter, abstract away the detail of CLAst. How would this look like? What would be the difference to the clast? Again, I do not say we don't need this, but it would be helpful if you can express why this is needed and what features it should have. In general I prefer to have as little code as possible. That means for every code we...

...s rather than assemble them in a single file (this will take time to do so and need to be well tested), I have made the first step of it in patch[1]. More steps will be done in the coming summer of code. 2. as you have post in the Todo list, the existing Polly back-end is currently centered on the CLAST. This will be another challenge to this project. 3. Another problem come up to me while I was fixing the bug of Polly[2]. The existing back-end use i64 everywhere to ensure a temporal correct result. Other project which may use date type larger than i64 may cause failure in Polly. So in the new co...

...quot; interface. 3. The auto-vectorization and parallelization codegen passes can just ask the common interface of "Parallelism Analysis" to get necessary information. The new approach may also make current work for OpenMP support esaier, Instead of generate the subfunction directly from clast and insert new function in a region pass(it seems that we can only insert new function in a modulepass or callgraphSCC pass), we can extract the body of the parallel for to a new function with existing CodeExtractor in LLVM. best regards ether

On 01/06/2011 03:38 AM, ether zhhb wrote: > Hi, > > I just have a detail look at the code of Polly[1], it seems that Polly > start to support some basic auto-parallelization stuffs. This is true. However still work in progress. I hope we can soon show some interesting results. > I have some idea to improve the current auto-vectorization > and parallelization approach in

Hi, I just have a detail look at the code of Polly[1], it seems that Polly start to support some basic auto-parallelization stuffs. I have some idea to improve the current auto-vectorization and parallelization approach in Polly. The main idea is, we separate the transform passes and codegen passes for auto-parallelization and vectorization (Graphite[2] for gcc seems to taking similar approach