similar to: [LLVMdev] LLVMdev Digest, Vol 55, Issue 16

The following C test program was compiled using LLVM with -O3 option and MSVC with /O2. The MSVC one is about 600 times faster than the one compiled with the LLVM. We can see that the for loop in MSVC assembler is solved in the optimization pass more efficiently than that in LLVM. Is there an way to get a optimization result in LLVM like that of the MSVC? Manoel Teixeira #include

The following C code : #include <stdio.h> #include <stdlib.h> int TESTE2( int parami , int paraml ,double paramd ) { int varx=0,vary; int nI =0; //varx= parami; if( parami > 0 ) { varx = parami; vary = varx + 1; } else { varx = vary + 1; vary = paraml; } varx = varx + parami + paraml; for( nI = 1 ; nI <= paraml; nI++) { varx =

Hi Manoel, > Hi, Duncan. > > Here an example : > #include <stdio.h> > #include <stdlib.h> > // > int TESTE ( int parami ,int paraml ) > { > int varx=0; > int nI =0; > > if( parami > 0 ) > { > varx = parami; > } > else > { > varx = 1; > } > > for( nI = 1 ; nI <= paraml;

hi all why does the following not work??? this was someone elses code and i couldnt explain why it doesn't work. m=matrix(c(0,0),2,1) v=matrix(c(1,0,0,1),2,2) Y=function(X1,X2,mu=m,V=v) { X=matrix(c(X1,X2),2,1) a=(1/((2*pi)*sqrt(det(V))))*exp((-0.5)*(t(X-mu)%*%solve(V)%*%(X-mu))) a[1] } x1=seq(-1,1) x2=x1 Z=outer(x1,x2,FUN="Y",mu=m,V=v) persp(x1,x2,Z) my code:

QUESTION: Is there a way of passing arguments from an external file to a script so that they can be used directly by functions within the script? I have a series of interdependent functions. I wish to test the time for processing various datasets. I was initially doing something along the lines of the following (yes, I am new to R): rm(list= ls())

You are completely correct - the DebugInfoBuilder class as it currently stands is only half finished. I've been meaning to work on it further, however before that can happen I need to actually try and use the basic block stuff in a real program so that I can get a feel for how it works and what the API should look like. It may be a while before I get around to doing that, however, so if

On Tue, Sep 22, 2009 at 9:21 AM, Devang Patel <devang.patel at gmail.com>wrote: > On Tue, Sep 22, 2009 at 9:21 AM, Devang Patel <devang.patel at gmail.com> > wrote: > > On Tue, Sep 22, 2009 at 12:14 AM, Talin <viridia at gmail.com> wrote: > >> So, one feature of the late, lamented DebugInfoBuilder that I am missing > >> quite badly, and which is not

DebugInfo.h is very light weight interface that allows one to manipulate llvm values that holds debugging information directly. On Jan 7, 2009, at 3:22 PM, Talin wrote: > Looking at DebugInfo.h, there are a couple of minor features that > DebugInfoBuilder that I would miss: > > 1) The ability to pass in an LLVM type and have it figure out the > size, alignment, etc. without

On Tue, Sep 22, 2009 at 4:49 PM, Talin <viridia at gmail.com> wrote: > > > On Tue, Sep 22, 2009 at 9:21 AM, Devang Patel <devang.patel at gmail.com> > wrote: >> >> On Tue, Sep 22, 2009 at 9:21 AM, Devang Patel <devang.patel at gmail.com> >> wrote: >> > On Tue, Sep 22, 2009 at 12:14 AM, Talin <viridia at gmail.com> wrote: >>

Looking at DebugInfo.h, there are a couple of minor features that DebugInfoBuilder that I would miss: 1) The ability to pass in an LLVM type and have it figure out the size, alignment, etc. without having to explicitly pass those values in as parameters to the builder call. 2) The ability for the size & alignment to be specified as Constants rather than as int64 so that the "gep

On Jan 7, 2009, at 3:22 AM, Patrick Boettcher wrote: > Hi list, > hi Talin, > > I'm working on a frontend to generate IR using the IRBuilder from > LLVM. > > Now I want to add source-level-debuginfo and for that I would like > to use the > DebugInfoBuilder as it is taking some of the burderns. Unfortunately > it does > not take all of them, yet. Instead

On Jan 7, 2009, at 1:48 PM, Talin wrote: > Fine by me :) Is it ok to remove DebugInfoBuilder now? I don't think that anything in the tree is using it, what do you think Talin? -Chris > > > On Wed, Jan 7, 2009 at 1:35 PM, Chris Lattner <clattner at apple.com> > wrote: > > On Jan 7, 2009, at 3:22 AM, Patrick Boettcher wrote: > > > Hi list, > >

Hi, I have the following problem with cbq.init script. I try to limit the output traffic from all my 254 IPs to 4Kb/s, but when I start the script the ping time from one of the shaped hosts drastically increases. 0,2-0,7 milisecs without shaper and 1500-2000 milisecs with. I though it might be the low CPU power or something. I''m running on 500MHz Intel Celeron. Anyone have experienced a

Fine by me :) On Wed, Jan 7, 2009 at 1:35 PM, Chris Lattner <clattner at apple.com> wrote: > > On Jan 7, 2009, at 3:22 AM, Patrick Boettcher wrote: > > > Hi list, > > hi Talin, > > > > I'm working on a frontend to generate IR using the IRBuilder from > > LLVM. > > > > Now I want to add source-level-debuginfo and for that I would like

Dear all, Being a newbie to R, I've trawled through many old posts on this list looking for a solution to my problem, but unfortunately couldn't quite figure it out myself. I'd be very grateful if someone here on this list could perhaps help me out. I have a lattice plot with several panels and would like to add some text next to the y-axis on the right hand side of each row of

On Sep 22, 2009, at 4:49 PM, Talin wrote: > > // Calculate the size of the specified LLVM type. > Constant * DebugInfoBuilder::getSize(const Type * type) { > Constant * one = ConstantInt::get(Type::Int32Ty, 1); > return ConstantExpr::getPtrToInt( > ConstantExpr::getGetElementPtr( > ConstantPointerNull::get(PointerType::getUnqual(type)), >

Hello, The CodeExtractor contains a std::set<BasicBlock*> to keep track of the blocks to extract. Iterators on this set are not deterministic, and so the functions that are generated are not (the order of the inputs/outputs can change). The attached patch uses a SetVector instead. Ok to apply ? Thanks, Julien -- Julien Lerouge PGP Key Id: 0xB1964A62 PGP Fingerprint: 392D 4BAD DB8B CE7F

Evan Cheng wrote: > I don't think so. Contribution welcome! :-) LLVM debugging support > isn't anywhere near where it needs to be. > Well, here's a rough sketch of what I was thinking of: class DebugInfoBuilder { public: /// Constructor DebugInfoBuilder(); /// Return the type defined by llvm.dbg.anchor.type StructType * GetAnchorType() const; ///

So, one feature of the late, lamented DebugInfoBuilder that I am missing quite badly, and which is not available in the current DIFactory, is the ability to specify structure offsets abstractly. The DebugFactory requires that you pass in structure offset information as ints, whereas DebugInfoBuilder had "offsetOf" and "alignOf" methods, similar to the "sizeOf"

On Fri, Jan 08, 2010 at 05:04:17PM -0800, Chris Lattner wrote: > On Jan 8, 2010, at 5:01 PM, Julien Lerouge wrote: > >Hello, > > > >The CodeExtractor contains a std::set<BasicBlock*> to keep track > >of the > >blocks to extract. Iterators on this set are not deterministic, and so > >the functions that are generated are not (the order of the >