similar to: [LLVMdev] Unnamed temporaries

On Fri, Mar 11, 2011 at 11:48 AM, Judison <judison at gmail.com> wrote: > I hope this is the right place to ask it, sorry if I'm wrong... It's the right place, though the IRC channel would have been good too. > My compiler is generating this code: > > (line numbers included) (Please ignore the extra br label %b0 and the whole > b0) Sorry, but the extra branches

Thank you John and John :P these optimizations (mem2reg and the "few additional" ones) I have to enable then or something like this?? (I compile the .ll to .o with the sequence llvm-as, llc, as) Yet about dynamic stack allocation, what is (generally) better? to pre alloc everything at start, or let it be? Imagine this pseudo-code while (x) { int b = 0; ... } using alloca where b

On Mar 14, 2011, at 5:56 PM, John Criswell wrote: > On 3/14/11 7:52 PM, Judison wrote: >> >> 2) does the LLVM optimizes this: >> >> ; this code (arg -> var) is very similar to what gcc generates >> define void @foo(i32 %arg0) { >> entry: >> %var0 = alloca i32 >> store i32 %arg0, i32* var0 >> ... >> %x = load i32*

Hi all, I have 2 simple questions... First, just for you to know, I'm making a compiler (kinda obvious) and the language definition is mine, so there is no much constraint for me, it's written in Java (it generates a .ll file as output) and it's just for fun by now, maybe a serious project after I learn all the stuff needed... and sorry bad english 1) I want to know if when I do

I'm trying to run a zero-inflated regression for a continuous response variable in R. I'm aware of a gamlss implementation, but I'd really like to try out this algorithm by Dale McLerran that is conceptually a bit more straightforward. Unfortunately, the code is in SAS and I'm not sure how to re-write it for something like nlme (if at all possible - with conditions etc). Does

On 3/14/11 7:52 PM, Judison wrote: > Hi all, > > I have 2 simple questions... > > First, just for you to know, I'm making a compiler (kinda obvious) and > the language definition is mine, so there is no much constraint for > me, it's written in Java (it generates a .ll file as output) and it's > just for fun by now, maybe a serious project after I learn all

Estimado Matías Epidemiología, no es un paquete, me refería a la parte de medicina, que por suerte en R hay herramientas que nos facilitan algunas de estas cuestiones. En http://cran.r-project.org/doc/contrib/Epicalc_Book.pdf hay un libro gratuito de R y epidemiología, aunque hay otros paquetes que tienen algunas cosas que pueden ser mejores, aunque muchas veces eso es a gusto personal o de

Hi, I was trying to use CloneBasicBlock() (in Cloning.h) to clone basic blocks in one of my transform passes. For example, when I have a basic block like: bb1: ; preds = %bb load i32* %i, align 4 ; <i32>:11 [#uses=2] load i32* %n_addr, align 4 ; <i32>:12 [#uses=2] icmp slt i32 %11, %12 ; <i1>:13 [#uses=2] cloning it gives something like: bb1_clone: ; preds = %entry

Hi, On 09/04/13 10:16, Dong Chen wrote: > hello guys: > I am in trouble with get the identifies of the unnamed temporaries from the > instruction of LLVM IR. this is a FAQ. Most names in the IR are just there to make it easier to read and can safely be removed. You can't rely on instructions having names, and as you saw often they do not have a name. Even if they start off with a

hi, Duncan Sands: thanks for your reply old friend. the reason why I want to get the unnamed value is that I am doing some analysis based on the IR code. And IR is in the form of SSA(static single assignment). so i need to get the operands of each instructions including a lot of instructions like this (%4 = mul nsw i32 %1, %width). the unnamed values are the connection of instructions, if i

Hi, On 09/04/13 11:19, Dong Chen wrote: > hi, Duncan Sands: > thanks for your reply old friend. > the reason why I want to get the unnamed value is that I am doing some > analysis based on the IR code. And IR is in the form of SSA(static single > assignment). so i need to get the operands of each instructions including a > lot of instructions like this (%4 = mul nsw i32 %1,

hi, Duncan: thanks for your patience. i have tried it. using instuction: errs()<<i->getOperand(0); but it prints the address: someting like 0x1139700; i checked the defination of getOperand() is Value* getOperand( unsigned int i); so is there someting i missed? -- View this message in context:

Hi, On 09/04/13 11:56, Dong Chen wrote: > hi, Duncan: > thanks for your patience. > i have tried it. > using instuction: errs()<<i->getOperand(0); errs()<<*i->getOperand(0); You can also use: i->getOperand(0)->dump(); Ciao, Duncan. > but it prints the address: someting like 0x1139700; > i checked the defination of getOperand() is Value* getOperand(

hi, Duncan, thank you for your reply; instruction "i->getOperand(0)->dump()" may print the %4 in the screen, but how can i store it in a variable like char * oprand="%4" ? -- View this message in context: http://llvm.1065342.n5.nabble.com/get-the-identifies-of-the-unnamed-temporaries-from-the-instruction-of-LLVM-IR-tp56572p56588.html Sent from the LLVM - Dev mailing

On Tue, Apr 9, 2013 at 12:47 PM, Dong Chen <jameschennerd at gmail.com> wrote: > hi, Duncan, > thank you for your reply; > instruction "i->getOperand(0)->dump()" may print the %4 in the screen, but > how can i store it in a variable like char * oprand="%4" ? > >

Tom Aernoudt via llvm-dev schrieb: > Hi all, > > The 'tmp' state variable is only needed during execution of the function > 'f'. > That's what you say, because you called it 'tmp' :), but the compiler sees no difference to 'a' or 'b'. As soon as s->tmp would "escape" f() the compiler will have to write it. I think you may

Hello, Before I get into troubles I ask here: I make a call to a C function using .C. What I would like to know is if the arguments in the .C call can also be 'temporary' objects. An example will illustrate this: # here we don't have a temporary Obj1 = 5 .C("Func", as.integer(Obj1 ), ...) # certainly works # here we do have a temporary Obj2 = 5 .C("Func",

hi Sean Silva: i really appriciate for your reply. but you konw that "dump()" instruction can print "%4" in the screen and each time print the same name "%4" not "%5" or "%6" for the same unnamed value. so there must be a way to determinate it. if "dump()" instruction can print it on the screen, can i find some way to store it in a char *

On 02/22/2011 14:01, Chuck Zhao wrote: > I wonder what is the right approach to obtain the address and size of > LLVM (compiler) generated temporaries? > > E.g. > > %0 = %x + %y > store i32 i0, i32 %z, align 4 > > How can I get the address of %0 (which could be either a stack or heap > variable)? > This is not possible since such value can also be in register.

hello guys: I am in trouble with get the identifies of the unnamed temporaries from the instruction of LLVM IR. for example: instruction: %4 = mul nsw i32 %1, %width unnamed temporaries: %4, %1 how to get them? I have tried several iterators(op_iterator,value_op_iterator) and getOperand(int) function,but none of them works. does anyone know how to get it? thanks very much -- View this message