similar to: [LLVMdev] obtain the address and size of LLVM generated temporaries

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.

I think I am overlooking a call or concept in R to help me easily and quickly restructure my data.frame:   Sometimes the data I receive looks like: VariableName, Run1, Run2, Run3, Location temp,               15.0,  16.0,  17.0, There   And other times it looks like: VariableName, Run, Location temp,               17.0, There   I would like to use the header information in order to be able to

Hi all, llvm-test fails on me in the first test (and many subsequent tests, but I hope that fixing the first test will allow me to continue). I see syntax errors from the C compiler and core dumps from llc. Is any of this supposed to happen? This is still on my amd64 machine. However, the build process is using the right incantation to compile (gcc-4.2 -m32 -Wl,-melf_i386). The llvm-gcc

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

Hi. I'm just starting to dig into the many existing llvm passes, and so far I didn't find what I'm looking for. I generate llvm IR code in debug. I'd just like to go through this code and remove as many temporaries as possible. Those variables look generated for debug purposes. They often look like synonyms of variables declared in the input source and don't seem to have a

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 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: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

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,

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" ? > >

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 *

Hi all, I have summarized the top 10 compiler passes for Polly when compiling LLVM test-ssuite. Results can be viewed on: https://gist.github.com/tanstar/581bcea1e4e03498f935/raw/f6a4ec4e8565f7a7bbdb924cd59fcf145caac039/Polly-top10 Based on the comparison between "clang -O3" and "polly -O3" listed on:

On 08/08/2013 01:29 AM, Star Tan wrote: > Hi all, > > > I have summarized the top 10 compiler passes for Polly when compiling LLVM test-ssuite. Results can be viewed on: > https://gist.github.com/tanstar/581bcea1e4e03498f935/raw/f6a4ec4e8565f7a7bbdb924cd59fcf145caac039/Polly-top10 > > > Based on the comparison between "clang -O3" and "polly -O3"

On 08/16/2013 02:42 AM, Star Tan wrote: > At 2013-08-16 12:44:02,"Tobias Grosser" <tobias at grosser.es> wrote: >> Hi, >> >> I tried to reproduce your findings, but could not do so. > > > Sorry, I did not put all code in my previous email because the code seems a little too long and complicated. > You can refer to the detailed C code and LLVM IR

On 07/29/2013 09:15 AM, Sven Verdoolaege wrote: > On Mon, Jul 29, 2013 at 07:37:14AM -0700, Tobias Grosser wrote: >> On 07/29/2013 03:18 AM, Sven Verdoolaege wrote: >>> On Sun, Jul 28, 2013 at 04:42:25PM -0700, Tobias Grosser wrote: >>>> Sven: In terms of making the behaviour of isl easier to understand, >>>> it may make sense to fail/assert in case

Hi Sebastian, Recently, I found the "Polly - Calculate dependences" pass would lead to significant compile-time overhead when compiling some loop-intensive source code. Tobias told me you found similar problem as follows: http://llvm.org/bugs/show_bug.cgi?id=14240 My evaluation shows that "Polly - Calculate dependences" pass consumes 96.4% of total compile-time overhead

The headers hadn't been regenerated in a long time, and there were a few minor divergences. Among other things, rnndb has changed naming to G80/etc, for now I've not tackled switching that over and manually replaced the nvidia codenames back to the chip ids. However no other modifications of the headergen'd headers was done. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>

Under certain circumstances, my compiler outputs basic blocks having the same function: bb_97: ; preds = %bb_1 %476 = getelementptr inbounds %LMtop.I0.ARType, %LMtop.I0.ARType* %0, i64 0, i32 6 %477 = bitcast i8** %476 to %LBstd.Cprocess.CRType** %478 = load %LBstd.Cprocess.CRType*, %LBstd.Cprocess.CRType** %477, align 8 %479 = getelementptr