search for: profileinfotyp

...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 lib/Analysis/ProfileEstimatorPass.cpp lib/Analysis/ProfileInfo.cpp lib/Analysis/ProfileInfoLoader.cpp lib/Analysis/ProfileInfoLoaderPass.cpp lib/Transforms/Instrumentation/* runtime/libprofile/* Also I would have to add some modules (new files) in Analysis, Transforms/Instrumentation and libpr...

...pt<bool> DotPathDag("dot-pathdag", + cl::desc("Output the path profiling DAG for each function.")); Please add cl::Hidden to all new flags, and give them all a "path-profile" prefix so they aren't scattered in the hidden help text. +++ include/llvm/Analysis/ProfileInfoTypes.h +#define PP_ARRAY 0 +#define PP_HASH 1 Why not an enum? +typedef struct { + unsigned fnNumber; /* function number for these counters */ + unsigned numEntries; /* number of entries stored */ +} PathHeader; + +typedef struct { + unsigned pathNumber; + unsigned pathCounter; +} PathTableE...

...athProfileInfo.h # deleted: include/llvm/Analysis/ProfileDataLoader.h # deleted: include/llvm/Analysis/ProfileDataTypes.h # deleted: include/llvm/Analysis/ProfileInfo.h # deleted: include/llvm/Analysis/ProfileInfoLoader.h # deleted: include/llvm/Analysis/ProfileInfoTypes.h # deleted: lib/Analysis/PathNumbering.cpp # deleted: lib/Analysis/PathProfileInfo.cpp # deleted: lib/Analysis/PathProfileVerifier.cpp # deleted: lib/Analysis/ProfileDataLoader.cpp # deleted: lib/Analysis/ProfileDataLoaderPass.cpp # deleted:...

...;dot-pathdag", > + cl::desc("Output the path profiling DAG for each function.")); > > Please add cl::Hidden to all new flags, and give them all > a "path-profile" prefix so they aren't scattered in the hidden help text. > > +++ include/llvm/Analysis/ProfileInfoTypes.h > > +#define PP_ARRAY 0 > +#define PP_HASH 1 > > Why not an enum? > > +typedef struct { > + unsigned fnNumber; /* function number for these counters */ > + unsigned numEntries; /* number of entries stored */ > +} PathHeader; > + > +typedef struct { &g...

I am a student at the University of Alberta under the supervision of José Nelson Amaral, and I have been working on implementing path profiling into LLVM. I have completed my project and would like to submit it. We are looking for a reviewer for the path profiling implementation. We have sent previous requests to the llvmdev list but have so far been unsuccessful. Please see the attached

...deleted: include/llvm/Analysis/ProfileDataLoader.h > # deleted: include/llvm/Analysis/ProfileDataTypes.h > # deleted: include/llvm/Analysis/ProfileInfo.h > # deleted: include/llvm/Analysis/ProfileInfoLoader.h > # deleted: include/llvm/Analysis/ProfileInfoTypes.h > # deleted: lib/Analysis/PathNumbering.cpp > # deleted: lib/Analysis/PathProfileInfo.cpp > # deleted: lib/Analysis/PathProfileVerifier.cpp > # deleted: lib/Analysis/ProfileDataLoader.cpp > # deleted: lib/Analysis/ProfileDataLoaderPass...

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't heard much from me yet.

...\..\include\llvm\Analysis\ProfileInfo.h"> > > </File> > > <File > > RelativePath="..\..\include\llvm\Analysis\ProfileInfoLoader.h"> > > </File> > > <File > > RelativePath="..\..\include\llvm\Analysis\ProfileInfoTypes.h"> > > </File> > > <File > > RelativePath="..\..\include\llvm\Analysis\ScalarEvolution.h"> > > </File> > > <File > > RelativePath="..\..\include\llvm\Analysis\ScalarEvolutionExpressions.h"&gt...

...is/PointerTracking.h -- Installing: /usr/local/llvm-2.8/include/llvm/Analysis/PostDominators.h -- Installing: /usr/local/llvm-2.8/include/llvm/Analysis/ProfileInfo.h -- Installing: /usr/local/llvm-2.8/include/llvm/Analysis/ProfileInfoLoader.h -- Installing: /usr/local/llvm-2.8/include/llvm/Analysis/ProfileInfoTypes.h -- Installing: /usr/local/llvm-2.8/include/llvm/Analysis/RegionInfo.h -- Installing: /usr/local/llvm-2.8/include/llvm/Analysis/RegionIterator.h -- Installing: /usr/local/llvm-2.8/include/llvm/Analysis/RegionPrinter.h -- Installing: /usr/local/llvm-2.8/include/llvm/Analysis/ScalarEvolution.h --...

On Thu, Sep 30, 2010 at 3:08 PM, Samuel Williams <space.ship.traveller at gmail.com> wrote: > Hi, > > I might just be doing something stupid, but when I do > > $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. > $ sudo make install > > I don't get the expected headers in >        /usr/local/llvm-2.8/include/llvm > > It is

...> RelativePath="..\..\include\llvm\Analysis\ProfileInfo.h"> > </File> > <File > RelativePath="..\..\include\llvm\Analysis\ProfileInfoLoader.h"> > </File> > <File > RelativePath="..\..\include\llvm\Analysis\ProfileInfoTypes.h"> > </File> > <File > RelativePath="..\..\include\llvm\Analysis\ScalarEvolution.h"> > </File> > <File > RelativePath="..\..\include\llvm\Analysis\ScalarEvolutionExpressions.h"> > </File> >...

Hi, I might just be doing something stupid, but when I do $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. $ sudo make install I don't get the expected headers in /usr/local/llvm-2.8/include/llvm It is simply an empty directory. What am I doing wrong? This is on Mac OS X, CMake 2.8+ Kind regards, Samuel