search for: creech

...ode generation using calls to POSIX threads. Since we currently have only a 2-person development team, we are still on LLVM 3.0, and some of the code could use some cleanup. Still, we hope that the work will be of interest to some. We would welcome any feedback, comments or questions! Thanks, Tim Creech

On 03/03/2013 02:09 PM, Timothy Mattausch Creech wrote: > Hi, > We would like to inform the community that we're releasing a version of our research compiler, "AESOP", developed at UMD using LLVM. AESOP is a distance-vector-based autoparallelizing compiler for shared-memory machines. The source code and some further informat...

...IR translator in a separate project. This has required new techniques specific to this problem. Aparna can provide more information on techniques used in our LMDA. -Tim On Sun, Mar 03, 2013 at 09:18:47AM +0100, Sebastian Dreßler wrote: > Hi, > > On 03/03/2013 07:09 AM, Timothy Mattausch Creech wrote: > > [...] > > The main components of the released implementation are loop memory > > dependence analysis and parallel code generation using calls to POSIX > > threads. > > The loop memory dependence analysis sounds very interesting to me. Could > you provide...

Hi, I've been patching OpenSSH [portable] so that I can override DESTDIR when cross-compiling. Is there any reason not to allow this in the general case? Thanks! -- Matthew L. Creech

----- Original Message ----- > From: "Timothy Mattausch Creech" <tcreech at umd.edu> > To: "Sebastian Dreßler" <dressler at zib.de> > Cc: "Aparna Kotha" <akotha at umd.edu>, llvmdev at cs.uiuc.edu > Sent: Sunday, March 3, 2013 11:32:49 AM > Subject: Re: [LLVMdev] AESOP autoparallelizing compiler > >...

Hi, On 03/03/2013 07:09 AM, Timothy Mattausch Creech wrote: > [...] > The main components of the released implementation are loop memory > dependence analysis and parallel code generation using calls to POSIX > threads. The loop memory dependence analysis sounds very interesting to me. Could you provide some more information regarding it...

...being parallelized > > Since A and B to function "func" are aliases it shouldn't have parallelized. > > Can you please let me know how you compute dependence ?? > > > Thanks, > Rahul > > > > On Sun, Mar 10, 2013 at 7:28 AM, Timothy Mattausch Creech <tcreech at umd.edu> wrote: > On Mon, Mar 04, 2013 at 03:01:15PM +0800, 陳韋任 (Wei-Ren Chen) wrote: > > Hi Timothy, > > > > > We would like to inform the community that we're releasing a version of our research compiler, "AESOP", developed at UMD using LLV...

Hi Tim, > From: Tim Creech <tcreech at umd.edu> > Subject: [LLVMdev] IVUsers (LoopPass) analysis in a ModulePass? > Date: September 1, 2011 11:46:28 AM PDT > To: llvmdev at cs.uiuc.edu > > Hi all, > I have a loadable ModulePass which does transformations, and I would like to > use IVUsers analysi...

...lized Loop func:for.body carries no dependence, hence is being parallelized Since A and B to function "func" are aliases it shouldn't have parallelized. Can you please let me know how you compute dependence ?? Thanks, Rahul On Sun, Mar 10, 2013 at 7:28 AM, Timothy Mattausch Creech <tcreech at umd.edu>wrote: > On Mon, Mar 04, 2013 at 03:01:15PM +0800, 陳韋任 (Wei-Ren Chen) wrote: > > Hi Timothy, > > > > > We would like to inform the community that we're releasing a version > of our research compiler, "AESOP", developed at UMD usin...

On Mon, Mar 04, 2013 at 03:01:15PM +0800, 陳韋任 (Wei-Ren Chen) wrote: > Hi Timothy, > > > We would like to inform the community that we're releasing a version of our research compiler, "AESOP", developed at UMD using LLVM. AESOP is a distance-vector-based autoparallelizing compiler for shared-memory machines. The source code and some further information is available at

Hi all, I have a loadable ModulePass which does transformations, and I would like to use IVUsers analysis within it. I noticed when I try to do this (via the usual addRequired<IVUsers>() and getAnalysis<IVUsers>(*F)), opt fails an assert: opt: /home/tcreech/build/llvm-2.9/include/llvm/PassAnalysisSupport.h:239: AnalysisType& llvm::Pass::getAnalysisID(const void*, llvm::Function&) [with AnalysisType = llvm::LoopInfo]: Assertion `ResultPass && "Unable to find requested analysis info"' failed. ...where I was using LoopInfo...

Trying to configure voicemail with H.323 all I get is the following errors when I call 123, 666, 665, 664 or 031. I'm a newbie at this so, I think it might be a simple fix. [chan_oh323.so] => (OpenH323 Channel Driver) == Parsing '/etc/asterisk/oh323.conf': Found 0:00.004 OpenH323 Wrapper OpenH323 Wrapper Version 0.0alpha0 by inAccess Networks