search for: alastairmurray42

...unces at cs.uiuc.edu] On Behalf Of Chandler Carruth Sent: Monday, July 16, 2012 6:34 AM To: Alastair Murray Cc: csdavec at swan.ac.uk; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] FYI: Planning to remove ProfileInfo and related passes from LLVM On Sun, Jul 15, 2012 at 8:32 AM, Alastair Murray <alastairmurray42 at gmail.com<mailto:alastairmurray42 at gmail.com>> wrote: Hi Chandler, I'm a GSoC student working on profiling support (mentor CC'ed). I'm no stranger to the issues with the current system: my original proposal was written without knowledge of the limitations. This is why t...

On Sun, Jul 15, 2012 at 8:32 AM, Alastair Murray <alastairmurray42 at gmail.com > wrote: > Hi Chandler, > > I'm a GSoC student working on profiling support (mentor CC'ed). I'm no > stranger to the issues with the current system: my original proposal was > written without knowledge of the limitations. This is why this list > hasn...

Hi David, You don't say which tests are failing, but they are probably ones I wrote (not many use libprofile_rt.so). On 08/01/13 11:18, dag at cray.com wrote: > I'm trying to validate some changes to send to trunk and I'm getting a > bunch of test failures like this: > > Error opening >

...ably a very simple script, but it does make it easier to see some preliminary profile results and identity the hot portions of a program which are suitable for hardware acceleration. llvm-prof also helps in the same way. Cheers, Alok ________________________________________ From: Alastair Murray [alastairmurray42 at gmail.com] Sent: Monday, 16 July, 2012 9:47:54 PM To: #ALOK PRAKASH# Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] FYI: Planning to remove ProfileInfo and related passes from LLVM Hi Alok, On 16/07/12 12:41, #ALOK PRAKASH# wrote: > I have been using the Profile.pl and the related passes...

I'm trying to validate some changes to send to trunk and I'm getting a bunch of test failures like this: Error opening '/ptmp/dag/build/llvm/staging/debug/Debug+Asserts/lib/libprofile_rt.so': /ptmp/dag/build/llvm/staging/debug/Debug+Asserts/lib/libprofile_rt.so: cannot open shared object file: No such file or directory Indeed there is no libprofile_rt.so. When I build from

Hi Alok, On 17/07/12 13:00, #ALOK PRAKASH# wrote: > Profile.pl is understandably a very simple script, but it does make > it easier to see some preliminary profile results and identity the > hot portions of a program which are suitable for hardware > acceleration. llvm-prof also helps in the same way. Ok, great -- using llvm-prof for detecting hot portions is the obvious use, but I

...) { *c = 8 + *a + *b; } extern void func(int N, const int *a, const int *b, int *c) { if ( __builtin_expect(N==2, 1) ) func2(N, a, b, c); else if ( __builtin_expect(N==4, 0) ) func4(N, a, b,c); else func8(N, a, b,c ); } Thanks, Evan On Jul 16, 2012, at 10:10 AM, Alastair Murray <alastairmurray42 at gmail.com> wrote: > Hi all, > > In light of the expected removal of ProfileInfo this is a request for > comments on the next few items that I now plan to work on for GSoC. > > Planned tasks: > > #0 Add support for determining branch weight metadata by profiling &g...

Hi Alok, On 16/07/12 12:41, #ALOK PRAKASH# wrote: > I have been using the Profile.pl and the related passes and > optimizations for about 4 years now. With every new release lately, the > support for the profile scripts and their framework seemed to be > downgrading. Hence, I used my own tiny one line fixes to keep them > working. I offered to send these small patches to keep these

Hi all, In light of the expected removal of ProfileInfo this is a request for comments on the next few items that I now plan to work on for GSoC. Planned tasks: #0 Add support for determining branch weight metadata by profiling At the absolute minimum this will require writing a new profile loader which will set branch weight metadata based on profiling data. #1 Optionally use profiling

Hi Chandler, I'm a GSoC student working on profiling support (mentor CC'ed). I'm no stranger to the issues with the current system: my original proposal was written without knowledge of the limitations. This is why this list hasn't heard much from me yet. I would like to continue working on profiling support but I'm not attached to ProfileInfo and wouldn't be

Hello folks, I'd like to remove all of the old and defunct profile info passes from LLVM. These have been almost entirely supplanted by the BranchProbability and BlockFrequency systems, which are actually on by default, and in use in optimization passes. The old system is not on, and hasn't been touched in years except to do minor build fixes and updates. As far as I'm aware, the

Hi David, On 18/09/12 11:21, David Tweed wrote: > in particular there are some regression tests of interesting things > -- such as profiling -- that fail purely because the default old JIT > doesn't work. I've actually got LLVM currently compiling within an ARM QEmu install to look at an assert within the ARM JIT code. Profiling tests that I submitted a few weeks ago are

Hi David, On 19/09/12 04:10, David Tweed wrote: > Yep, this is the issue. Running on an ARM pandaboard I can confirm that it's > due to issues with the old JIT in general which are fixed in MCJIT, and > nothing to do with the profiling code being tested, as discussed in this > thread: > > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120910/150406. > html

Hi Silky, Sorry for the slow reply. You probably already fixed this, but just in case I'll reply anyway. Comments inline below On 15/01/13 19:38, SArora wrote: > Hi Alastair, > Thank you so much for the information on the tools. Actually, I need to > analyze which sections of code are prone to misses and mis predicts, and > would have to eventually instrument the code. >

Hi Apala, On 11/09/12 11:20, apala guha wrote: > Is it possible to associate the branch frequency counts with the basic > blocks > in the intermediate representation? (e.g. Can I access basic block > frequencies in runOnFunction()?) Profile data really needs to be loaded at a module level, but once this has been done it can be accessed at any level (including function). In LLVM

Hi Silky, On 14/01/13 01:47, Silky Arora wrote: > I need to profile the code for branches (branch mis predicts > simulation), load/store instructions (for cache hits/miss rate), and a > couple of other things and therefore, would need to instrument the code. > However, I would like to know if writing the output to a file would > increase the execution time, or is it the profiling

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 Apala, Dibyendu is correct that this is likely due to pass order, but things get a bit complicated with -O[1-9] or -std-compile-opts as they insert early passes *before* the profiling code. I recommend that you use identical optimizations to insert instrumentation and to load the profiling data. E.g.: opt -insert-edge-profiling -O3 foo.bc -o foo.2.bc opt -profile-loader -O3 foo.bc

Hello Everyone, Before I get started I just want to sincerely apologise for not getting feedback on this earlier. I've had an extremely busy week as I was presenting a paper at the CGO conference. If anyone is able to provide feedback in such a short time-frame then it will be gratefully received. If not, then I just hope the work described sounds useful. I have already submitted