search for: functionutil

...; On Jan 2, 2009, at 12:21 PM, Misha Brukman wrote: > Do you have a specific example of a unit test that would need these? I > really think these should stay private. > Let's take lib/Transforms/Utils/CodeExtractor.cpp . The public interface for it is in include/llvm/Transform/Utils/FunctionUtils.h, with only the high-level API. If I want to test some corner-case (consider the number of code paths in that code), I have to strain to come up with some combination of a Function and input BasicBlocks that will fit all the conditions from the outset. Or, I can just feed each individual method...

...all label > code C > > function label: > code B > > I think I have a pretty good idea of how to do this (BasicBlock::split > really helps!), but I have a few specific questions: Evan, Have you looked at ExtractCodeRegion() and its siblings in include/llvm/Transform/Utils/FunctionUtils.h? It seems to be what you need. --Vikram http://www.cs.uiuc.edu/~vadve http://llvm.cs.uiuc.edu/

On Apr 19, 2005, at 22:10, Evan Jones wrote: > I just found the Interval class, and it looks like it could help me > out here. I want to locate the Interval that begins with the call to > the "magic" begin(), and ends with the call to the "magic" end(), if > it exists. If there is no such valid interval, then I want to detect > that and return an error. Can I

...009, at 12:21 PM, Misha Brukman wrote: > Do you have a specific example of a unit test that would need > these? I really think these should stay private. > > Let's take lib/Transforms/Utils/CodeExtractor.cpp . The public > interface for it is in include/llvm/Transform/Utils/FunctionUtils.h, > with only the high-level API. > > If I want to test some corner-case (consider the number of code > paths in that code), I have to strain to come up with some > combination of a Function and input BasicBlocks that will fit all > the conditions from the outset. Or, I...

...PM, Misha Brukman wrote: >> Do you have a specific example of a unit test that would need these? I >> really think these should stay private. >> > > Let's take lib/Transforms/Utils/CodeExtractor.cpp . The public interface > for it is in include/llvm/Transform/Utils/FunctionUtils.h, with only the > high-level API. > > If I want to test some corner-case (consider the number of code paths in > that code), I have to strain to come up with some combination of a Function > and input BasicBlocks that will fit all the conditions from the outset. Or, > I can jus...

Dear all, I want to move a block of instructions from its original function, form a new function, and place these instructions in the new function. these blocks of instructions are not bound by Basic Blocks, i mean i can cut Basic Blocks and move only part of it to the new function. I guess the solution can be either clone the whole function and start deleting instructions from the two

...>> Do you have a specific example of a unit test that would need these? I > >> really think these should stay private. > >> > > > > Let's take lib/Transforms/Utils/CodeExtractor.cpp . The public interface > > for it is in include/llvm/Transform/Utils/FunctionUtils.h, with only the > > high-level API. > > > > If I want to test some corner-case (consider the number of code paths in > > that code), I have to strain to come up with some combination of a Function > > and input BasicBlocks that will fit all the conditions from the ou...

On Jan 2, 2009, at 12:21 PM, Misha Brukman wrote: > Hi all, > > Reading this doc: http://llvm.org/docs/CodingStandards.html#hl_privateheaders > , it suggests putting private implementation details outside of llvm/ > include/* to avoid polluting the public header space. This makes > sense, and it works fine, because make enters every directory and > hence doesn't

On Apr 19, 2005, at 23:17, Vikram Adve wrote: > Have you looked at ExtractCodeRegion() and its siblings in > include/llvm/Transform/Utils/FunctionUtils.h? It seems to be what you > need. This is brilliant. In fact, it is nearly *exactly* what I need. On Apr 19, 2005, at 23:59, Chris Lattner wrote: > An Interval (and an Interval partition) is a concept with a lot of > compiler theory behind it. If you google for control flow analys...

Hi all, Reading this doc: http://llvm.org/docs/CodingStandards.html#hl_privateheaders, it suggests putting private implementation details outside of llvm/include/* to avoid polluting the public header space. This makes sense, and it works fine, because make enters every directory and hence doesn't need a -I path to include them. However, unittests need to also #include these headers to be

...- Installing: /usr/local/llvm-2.8/include/llvm/Transforms/Utils/BasicInliner.h -- Installing: /usr/local/llvm-2.8/include/llvm/Transforms/Utils/BuildLibCalls.h -- Installing: /usr/local/llvm-2.8/include/llvm/Transforms/Utils/Cloning.h -- Installing: /usr/local/llvm-2.8/include/llvm/Transforms/Utils/FunctionUtils.h -- Installing: /usr/local/llvm-2.8/include/llvm/Transforms/Utils/Local.h -- Installing: /usr/local/llvm-2.8/include/llvm/Transforms/Utils/PromoteMemToReg.h -- Installing: /usr/local/llvm-2.8/include/llvm/Transforms/Utils/SSAUpdater.h -- Installing: /usr/local/llvm-2.8/include/llvm/Transforms/Uti...

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

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

...ath="..\..\include\llvm\Transforms\Utils\BasicBlockUtils.h"> > </File> > <File > RelativePath="..\..\include\llvm\Transforms\Utils\Cloning.h"> > </File> > <File > RelativePath="..\..\include\llvm\Transforms\Utils\FunctionUtils.h"> > </File> > <File > RelativePath="..\..\include\llvm\Transforms\Instrumentation.h"> > </File> > <File > RelativePath="..\..\include\llvm\Transforms\IPO.h"> > </File> > <File >...