search for: diken

...ill benefit from delinearization and am hoping it >> gets incorporated soon. >> >> If someone could review this change and check it in, if appropriate, I'd >> be obliged. >> >> Thanks, >> Preston >> >> >> > -- Best Regards, Erkan Diken ------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121113/8a489d59/attachment.html>

On 13.11.2012, at 10:46, erkan diken <erkandiken at gmail.com> wrote: Hi all, Unfortunately, all my Hunks are failed when I apply : patch -p1 < da.patch command. The problem might be due to the fact that da.patch file was created against revision 167549, but I am on revision 167719 (I believe the most recent one). I am not...

erkan diken <erkandiken at gmail.com> writes: [snip] > It seems that cmake is ok. When I run make install, it gives errors (see > below) and i think the reason is that it can not find the directory to llvm > header files. > I could not figure it out which variable to set and how to use it i...

...mico > ______________________________**_________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/**mailman/listinfo/llvmdev<http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev> > -- Best Regards, Erkan Diken ------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130808/49e1291d/attachment.html>

Hello, I'm currently trying to develop new LLVM Pass that will generate simple data dependencies graph. For now I'm trying to get familiar with DependenceAnalysis. My general idea is to traverse each function (runOnFunction) top to bottom Instruction by Instruction, using DA.depends( I, I2, ...) on every Instructions combination in function to check if they are dependent on any

Dear all, I want to build an LLVM pass by using CMake. After reading the ralevant part of the documentation ( http://llvm.org/releases/3.1/docs/CMake.html#passdev), I copied the files in the llvm/lib/Transforms/Hello to another folder in order to give a try. Then I renamed the folder as Hello2. Then I have changed CMakeLists.txt as following: cmake_minimum_required(VERSION 2.8) # A

...is messing up my work as well..I am trying to fix it now.. If you could give me the exact details of the error and your steps, I might be able to work it out... Cheers, Alok ________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on behalf of erkan diken [erkandiken at gmail.com] Sent: Wednesday, 18 April, 2012 5:15:42 PM To: llvmdev at cs.uiuc.edu Subject: [LLVMdev] how to get path profile information ? Dear all, I have already checked some related posted messages, such as: http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-January/012315.html and...

Dear all, I have already checked some related posted messages, such as: http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-January/012315.html and http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-February/012466.html After getting rid of some error messages, I was able to run the following commands: 1) opt -insert-path-profiling matmul.bc -o matmul.pp.bc 2) lli -load

...omise is to be kept. You promise on rx m,`ed~s with f'a'st del.i^very is really kept and I can really relax and use your service interface f.r,eely n._ow. All the previous worries are all gone n_-ow. --Cynthia O. SD bem?je17 dobbelttilv?relsens 07 b?ltested beregningsform dommedagspr?dikeners fashion, or the custom of the age:36 there are

Hi, all ! I am doing some study about code generation in LLVM, It is a pity that there is little introduction to it. Some paper introduces that code generation in LLVM is based on Table Driven, and i have referred paper "*An experiment in table driven code generation*", But it has not given me any help. Can you give a help understanding the code generation in LLVM. Thanks a lot.

Hi Guys, I noticed that the operation actions( promote/expand/custom) are set per operation basis. Wondering if we can set it up globally? For example, I have native supported 32 bits registers, to handle 8 bits value operations, I want to do promote. and to support 64 bit operations, I want to expand. If I can set up the operation actions for the same type globally, then I can avoid to

Hi everyone! Here, I have a question and am curious about i128. I want to know how the LLVM handle i128, because many compiler backend doesn't support i128 directly. So I am very curious and want to how the llvm handle this situation? Besides i128, such as i256, i512, even i24? Thanks. Best Regards Wu Zhao -------------- next part -------------- An HTML attachment was scrubbed...

Preston, thanks for the explanation and patch. Now it's printing the direction and distance values. On Tue, Nov 13, 2012 at 12:22 PM, Preston Briggs <preston.briggs at gmail.com>wrote: > Erkan, you're right. Sorry about that. > Attached is the most recent version. > > Preston > > > > Hi Preston, >> I am trying to use DA as well. I used your example

Erkan, you're right. Sorry about that. Attached is the most recent version. Preston Hi Preston, > I am trying to use DA as well. I used your example and commands that you > wrote in order to get DA information. > However, it does not report any dependence info. > I am wondering whether your local copy differs from the one on the > repository ? > Thanks. > Erkan.

Hi, The DependenceAnalysis pass will find loop-carried dependences. However, it is a conservative analysis and will sometimes suggest there may be more dependences than actually exist. In your example, I expect the analysis is confused for some reason and is returning the default confused response. You could test it using the isConfused() method. Note that the DVEntry::ALL direction is always

Dear all, I am trying to build the llvm with cmake and using the following checkouts. LLVM version 3.2svn clang version 3.2 (trunk 158320) (llvm/trunk 158308) cmake runs with default configuration without any problem. cmake ../llvm -- Target triple: i686-pc-linux-gnu -- Native target architecture is X86 -- Threads enabled. -- Building with -fPIC -- Constructing LLVMBuild project information --