search for: bolka

Displaying 15 results from an estimated 15 matches for "bolka".

2009 Apr 01
1
[LLVMdev] GSoC 2009: Auto-vectorization
Hi Stefanus, On Wed Apr 01 16:08:45 +0200 2009, Stefanus Du Toit wrote: > On 31-Mar-09, at 8:27 PM, Andreas Bolka wrote: > > i.e. the core of the desired result would look like: > > > > %va = load <256 x i32>* %a > > %vb = load <256 x i32>* %b > > %vc = add <256 x i32> %a, %b > > store <256 x i32> %vc, <256 x i32>* %c > > I thi...
2009 Apr 01
8
[LLVMdev] GSoC 2009: Auto-vectorization
...with the concepts behind auto-vectorization, I haven't implemented an auto-vectorizer before. I'm author of and contributor to several smaller open source projects. I appreciate any suggestions and would be very excited if someone is interested in mentoring this. -- Best regards, Andreas Bolka
2009 May 15
0
[LLVMdev] Loop-carried Dependence
Hi Wenhao Jia, On Wed May 13 16:30:36 +0200 2009, Wenhao Jia wrote: > Does anyone know if there is any existing code I can use to do a > loop-carried dependence analysis for LLVM IR programs? I searched the > mailing-list archive and it seems like someone planned to implement a > loop dependence analysis pass in March. I'm just wondering if this > project is ongoing/finished or
2010 Mar 27
0
[LLVMdev] [repository] Make LLVM repository Git-clonable
On Sat Mar 27 21:38:52 +0100 2010, Michel Alexandre Salim wrote: > There are LLVM Git mirrors (there's one on GitHub, and I used to have > a personal clone too) but they all track only the trunk directory The Git mirror I maintain at http://github.com/earl/llvm-mirror has releases branches (and tags), currently going back to the 2.0 release. Once 2.7 is released, I'll add the
2009 May 13
2
[LLVMdev] Loop-carried Dependence
Hi, Does anyone know if there is any existing code I can use to do a loop-carried dependence analysis for LLVM IR programs? I searched the mailing-list archive and it seems like someone planned to implement a loop dependence analysis pass in March. I'm just wondering if this project is ongoing/finished or if there is other projects that may have the code I'm interested in. Thanks!
2009 Apr 01
0
[LLVMdev] GSoC 2009: Auto-vectorization
Hi Andreas, On 31-Mar-09, at 8:27 PM, Andreas Bolka wrote: > So, initially, I aim at supporting only the simplest loops such as: > > int a[256], b[256], c[256]; > for (int i = 0; i < 256; ++i) > c[i] = a[i] + b[i]; > > My goal is to implement the necessary analyses and transformations to > turn IR corresponding...
2010 Mar 27
4
[LLVMdev] [repository] Make LLVM repository Git-clonable
Hi, As a Linux package maintainer I tend to follow LLVM mostly towards the end of each release cycle; nevertheless, I sometimes need to keep track of multiple LLVM branches at the same time. It would be great if I could use Git's SVN to clone the repository once, and then have the full version history available locally in a compact format. As a bonus, this will reduce the load on the server
2009 Apr 01
1
[LLVMdev] GSoC 2009: Auto-vectorization
Hi Chris, On Wed Apr 01 08:18:28 +0200 2009, Chris Lattner wrote: > On Mar 31, 2009, at 5:27 PM, Andreas Bolka wrote: > > My goal is to implement the necessary analyses and transformations to > > turn IR corresponding to such code into IR utilizing vector > > instructions; > > Sounds great. Some important steps: > 1. We need an abstract dependence analysis interface (like we ha...
2009 Apr 01
0
[LLVMdev] GSoC 2009: Auto-vectorization
Andreas Bolka wrote: > Hi all, > > I'd like to have a first stab at a loop-based auto-vectorization pass as > part of 2009's Google Summer of Code program. As far as I can tell from > searching the mailing list archives, no work on such an auto-vectorizer > seems to be currently in pro...
2009 Apr 01
0
[LLVMdev] GSoC 2009: Auto-vectorization
On Mar 31, 2009, at 5:27 PM, Andreas Bolka wrote: > Hi all, > I'd like to have a first stab at a loop-based auto-vectorization > pass as > part of 2009's Google Summer of Code program. As far as I can tell > from > searching the mailing list archives, no work on such an auto- > vectorizer > seems to be c...
2010 Apr 01
0
[LLVMdev] AnalysisUsage: addRequired vs. addRequiredTransitive
On Fri Apr 02 00:37:03 +0200 2010, Trevor Harmon wrote: > On Mar 31, 2010, at 3:13 PM, Owen Anderson wrote: > > Others, like MemoryDependenceAnalysis, are "lazy." MDA > > specifically does NOT compute results in its runOnFunction(), > > instead computing results on-demand when a user queries it. Because > > MDA depends on AA, we must ensure that, as long as
2010 Apr 01
2
[LLVMdev] AnalysisUsage: addRequired vs. addRequiredTransitive
On Mar 31, 2010, at 3:13 PM, Owen Anderson wrote: > Some analyses, like Andersen's AA, do all their computation in their > runOnFunction(). Therefore, anything they depended on can be > destroyed after the runOnFunction() returns. What about AA itself? Would addRequired<AliasAnalysis> keep AliasAnalysis alive (but allow AliasAnalysis's dependencies to die)? >
2009 Apr 01
2
[LLVMdev] GSoC 2009: Auto-vectorization
Nick Lewycky wrote: > Andreas Bolka wrote: >> Hi all, >> >> I'd like to have a first stab at a loop-based auto-vectorization pass as >> part of 2009's Google Summer of Code program. As far as I can tell from >> searching the mailing list archives, no work on such an auto-vectorizer >> seems...
2009 Aug 04
0
[LLVMdev] Mirroring of LLVM repository
On Tue Aug 04 20:56:18 +0200 2009, Rafael Espindola wrote: > >    git clone git://github.com/earl/llvm-mirror.git llvm > >    cd llvm > >    git config --add remote.origin.fetch '+refs/remotes/*:refs/remotes/*' > >    git fetch > >    git svn init https://llvm.org/svn/llvm-project/llvm/trunk > >    git svn rebase --local > > This one worked
2009 Aug 04
0
[LLVMdev] Mirroring of LLVM repository
On Mon Aug 03 21:09:59 +0200 2009, Anton Korobeynikov wrote: > Currently the load of llvm.org is too high. This influences the whole > project services like buildbots, bugzilla, etc. It was found that this > workload is possible caused by massive mirroring of LLVM SVN > repository into git/hg/whatever. Please don't do that :) Let me add to what Anton said: I can only speak for