search for: esaier

Displaying 4 results from an estimated 4 matches for "esaier".

Did you mean: easier
2011 Jan 07
1
[LLVMdev] Proposal: Generic auto-vectorization and parallelization approach for LLVM and Polly
...ese information via the common "Parallelism Analysis" 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 eth...
2004 Sep 10
2
Bug with FLAC raw encoding
On Fri, 2 Feb 2001, Josh Coalson wrote: > sounds great. I've been thinking about adding a > 'what uses FLAC' set of links to the web page... > please keep me posted. The latest version of my cue+wav splitter supports .flac files. Hope to get it released this weekend. Will eventually be at: www.lameb.fsnet.co.uk It also supports .shn and .ape. I've seen shorten
2011 Jan 06
0
[LLVMdev] Proposal: Generic auto-vectorization and parallelization approach for LLVM and Polly
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
2011 Jan 06
3
[LLVMdev] Proposal: Generic auto-vectorization and parallelization approach for LLVM and Polly
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