similar to: [LLVMdev] Use LoopInfo in a non-pass class such as ProfileInfoLoader?

Hi John, My project is somewhat inbetween, but closer to the latter. If you are doing something related to synthesis, have you checked xPilot from UCLA? Search "llvm" in this paper <http://www.icims.csl.uiuc.edu/~dchen/xpilot-TechCon2005.pdf> Anyway, thanks for the information! :-) Wenhao On Tue, Mar 3, 2009 at 6:30 AM, <llvmdev-request at cs.uiuc.edu> wrote: > >

Hi, Does anyone know any tool that can help generate a control/data flow graph (CDFG) for LLVM IR programs? The opt -view-cfg and related commands can visualize a program as a control flow graph. But how can I embody data flow information into that graph? Your help will be greatly appreciated! Thanks, Wenhao Jia -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Wenhao Jia, On Wed May 13 16:30:36 +0200 2009, Wenhao Jia wrote: > Does anyone know if there is any existing code I can use to do a > loop-carried dependence analysis for LLVM IR programs? I searched the > mailing-list archive and it seems like someone planned to implement a > loop dependence analysis pass in March. I'm just wondering if this > project is ongoing/finished or

Hi, Does anyone know if there is any existing code I can use to do a loop-carried dependence analysis for LLVM IR programs? I searched the mailing-list archive and it seems like someone planned to implement a loop dependence analysis pass in March. I'm just wondering if this project is ongoing/finished or if there is other projects that may have the code I'm interested in. Thanks!

Hi, I have trouble making my ProfileInfo-Analysis available in the backend, I have changed llc so it loads the ProfileInfo if requested, the PassManger gives this output: > Target Data Layout > Create Garbage Collector Module Metadata > Basic Alias Analysis (default AA impl) > DWARF Information Writer > No Profile Information > Module Information > ModulePass

Hi, this is the first in a series of patches to cleanup and improve the LLVM Profiling Infrastructure. First and foremost this patch removes duplicate functionality from ProfileInfoLoader and ProfileInfo: The ProfileInfoLoader performed not only the loading of the profile information but also some synthesis of block and function execution counts from edge profiling information. Since the

Hi, Devang Patel wrote: > On Tue, Nov 17, 2009 at 9:03 AM, Andreas Neustifter > <astifter-llvm at gmx.at> wrote: > >> Okay, so the ProfileInfoLoader is working, but when I examine the executions more closely I see that the ProfileInfo generated by the ProfileInfoLoader is immediately discarded, when the SelectionDAGISel kicks in the "No Profile Info"-Implementation

Hello, I used optim to find the MLE estimates of some parameters. See the code below. It works for data1(x). but It did not work for data2 and the error says" L-BFGS-B needs finite values of 'fn' ". data2: c(x, 32) that is, if I added the number 32 at the end of data1. The error appears "non-finite function value" etc. Any comments or suggestions? Thanks!

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, since I'm planing on a whole bunch of changes in the area of the Profiling Infrastructure I would like to ask humbly if it is possible to have approve-after-commit permission for the following files: include/llvm/Analysis/ProfileInfo.h include/llvm/Analysis/ProfileInfoLoader.h include/llvm/Analysis/ProfileInfoTypes.h

On Tue, Nov 17, 2009 at 9:03 AM, Andreas Neustifter <astifter-llvm at gmx.at> wrote: > > Okay, so the ProfileInfoLoader is working, but when I examine the executions more closely I see that the ProfileInfo generated by the ProfileInfoLoader is immediately discarded, when the SelectionDAGISel kicks in the "No Profile Info"-Implementation is used: > >  > 0x1c1a740  

Hi Andreas, Thanks for breaking things up. I applied two pieces of this patch in separate no-functionality-change commits, here: http://llvm.org/viewvc/llvm-project?view=rev&revision=75623 and here: http://llvm.org/viewvc/llvm-project?view=rev&revision=75625 I merged in my changes to your patch, which results in the attached patch. There may be some missed merge errors. The main

Hi. On 11/17/2009 08:16 PM, Andreas Neustifter wrote: > Hi, > > Devang Patel wrote: >> On Tue, Nov 17, 2009 at 9:03 AM, Andreas Neustifter >> <astifter-llvm at gmx.at> wrote: >> >>> Okay, so the ProfileInfoLoader is working, but when I examine the executions more closely I see that the ProfileInfo generated by the ProfileInfoLoader is immediately

Hi, I have a doubt regarding *getAnalysisUsage.* My assumption is that, as analysis passes will not change the IR, all the passes required by an analysis pass should be preserved. Say, I have an analysis pass which requires another analysis pass called *SomeAnalysis* and I have not added *AU.addPreserved<SomeAnalysis>() *to my pass. Would the pass manager still considers the *SomeAnlaysis

Alright, I'm ready to nuke it. Last chance to say stop. For context of others, this has come up repeatedly: no one we know of is using EdgeProfiling.cpp, PathProfiling.cpp, and the lib/Analysis/Profile*Pass.cpp collection of tools. They haven't been updated since 2012 when Alastair Murray looked into this stuff, and both current efforts towards PGO are essentially *totally* different

Hello, I merged my test commit successfully. (./utils/release/merge.sh --proj llvm --rev 46043 -srcdir ../llvm/) ... D46043 as "Merging r46043" https://reviews.llvm.org/rL330799 But I have issues with other patch - https://reviews.llvm.org/D45418 I ran ./utils/release/merge.sh --proj llvm --rev 45418 -srcdir ../llvm/ # Updating tree Updating '.': At revision 330799. #

Hi all, Attached is a draft patch to use profiling data to set branch weight metadata. I'm not formally submitting this as a patch yet as it does not make much sense to add it before ProfileInfo etc. is removed. I am, however, interested in making sure this is the correct approach to be taking, or any other feedback. (Also, there are a few TODO notes in there which would not be in the

Hi Alastair, Your patch looks great. I am new on this part of llvm. Why do we want to get rid of ProfileInfo? Is there any email thread related to this? I understand that we want to setBranchWeightMetadata from the profiling data generated by -insert-edge-profiling. I thought the existing loader can parse the profiling data and map the data to the IR, and only the setting of metadata is missing.

Hi Daniel, Daniel Dunbar wrote: > Hi Andreas, > > First, thanks again for undertaking this work and submitting it back. There is a > lot of good stuff here and it would be great to see it get back into the tree. Thanks for taking the time to review this, I know its a huge patch. I still have a few questions on how you would like this patch to be re-factored and split up. > [...]

Hi all, as proposed in http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-February/020396.html I implemented the algorithm presented in [Ball94]. It only instruments the minimal number of edges necessary for edge profiling. The main changes introduced by this patch are: *) a interface compatible rewrite of ProfileInfo *) a cleanup of ProfileInfoLoader (some functionality in ProfileInfoLoader

The merge.sh script is used to merge SVN commits to the release branch. It sounds like what you want to do is commit patches from Phabricator to trunk? If that's the case, see https://llvm.org/docs/Phabricator.html#committing-a-change On Wed, Apr 25, 2018 at 10:29 AM, Dávid Bolvanský via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hello, > > I merged my test commit