search for: runon

>I hear ya. I guess what I was getting at was that I couldn't see much > hope of getting Asterisk to natively support proprietary sets, It is not that I want to use proprietary phones, I want the benefits that native digital phones will provide. This will allow Asterisk to work more effectively in office environments. As to the quad or octo BRI ports, I'm looking for more phone

Dear Owen, Are passes supposed to grab the LLVMContext from the Module/Function/BasicBlock passed into their runOn<Module/Function/BasicBlock> method, or is the PassManager supposed to set the pass's Context member variable automatically? I thought it was the latter, but after an SVN update of LLVM, my passes have a NULL Context, and the LLVM code looks like the passes are all setting their Context m...

...<http://llvm.org/docs/WritingAnLLVMPass.html#LoopPass>) >> is misleading or >> incorrect (or if I'm just missing something.) The documentation states: >> >> "The doFinalization method ... is called when the pass framework has >> finished >> calling runOnLoop <http://llvm.org/docs/**WritingAnLLVMPass.html#** >> runOnLoop <http://llvm.org/docs/WritingAnLLVMPass.html#runOnLoop>> for >> >> every loop in the program being compiled." >> >> From this, I understood that for a single instance of a LoopPass &gt...

...;http://llvm.org/docs/WritingAnLLVMPass.html#LoopPass>) is misleading or > incorrect (or if I'm just missing something.) The documentation states: > > "The doFinalization method ... is called when the pass framework has > finished > calling runOnLoop > <http://llvm.org/docs/__WritingAnLLVMPass.html#__runOnLoop > <http://llvm.org/docs/WritingAnLLVMPass.html#runOnLoop>> for > > every loop in the program being compiled." > > From this, I understood that for a single instance...

...e structural hash of the function has changed, and complains that the pass didn’t correctly report that it changed the function [4] (even though materially, it didn’t). This raises a broader question of what we really mean when we say that a pass is allowed to report it made no changes through its runOn* function(s): A) The obvious, and most restrictive condition would be that the pass can only return false if it treated the Function/Module/etc that it visited purely as read-only. From what I can tell, a lot of passes conservatively assume this is the required condition. B) Less obvious would be...

Dear John, I think you must call (YourPassManager)->doInitialization() to set the LLVMContext object. Nicolas John Criswell wrote: > Dear Owen, > > Are passes supposed to grab the LLVMContext from the > Module/Function/BasicBlock passed into their > runOn<Module/Function/BasicBlock> method, or is the PassManager supposed > to set the pass's Context member variable automatically? > > I thought it was the latter, but after an SVN update of LLVM, my passes > have a NULL Context, and the LLVM code looks like the passes are all >...

Hello, is there any way I can access CallGraph from immutable pass via getAnalysis? As I understand it, this may not be possible, because immutable pass don't have runOn method and is never actually planned. But I'm not 100% sure how this works, so I don't know if there is some other way. Thanks, Robert Barucak

...execution from the rest of the infrastructure > so the class need not be visible to anything outside the > implementation > of the pass itself. Even though the PassManager implements the Hollywood Principle, something outside of the pass implementation still has to invoke one of the runOn* functions. And I'm not understanding how this invocation can occur if the implementation is invisible. Maybe I should just chalk this up to template magic... On a related note, the source code comments in PassSupport.h (line 156) say that the RegisterPass instance should be declared in...

...r > example, give you the number of bytes used to store a type. > > Read the document on Writing an LLVM Pass > (http://llvm.org/docs/WritingAnLLVMPass.html) to learn how to have your > pass declare the TargetData pass as a prerequisite and to get a pointer > to it when your > runOnFunction/runOnModule/runOnBasicBlock/runOn<whatever> method is > called. Then use the doxygen documentation to find the correct method > of the TargetData pass > (http://llvm.org/doxygen/classllvm_1_1TargetData.html) to use to get the > size of the type that you allocated via all...

...ne specific information and can, for example, give you the number of bytes used to store a type. Read the document on Writing an LLVM Pass (http://llvm.org/docs/WritingAnLLVMPass.html) to learn how to have your pass declare the TargetData pass as a prerequisite and to get a pointer to it when your runOnFunction/runOnModule/runOnBasicBlock/runOn<whatever> method is called. Then use the doxygen documentation to find the correct method of the TargetData pass (http://llvm.org/doxygen/classllvm_1_1TargetData.html) to use to get the size of the type that you allocated via alloca. -- John T. &...

...of the function has changed, and complains that the pass didn’t correctly report that it changed the function [4] (even though materially, it didn’t). >> >> This raises a broader question of what we really mean when we say that a pass is allowed to report it made no changes through its runOn* function(s): >> >> A) The obvious, and most restrictive condition would be that the pass can only return false if it treated the Function/Module/etc that it visited purely as read-only. From what I can tell, a lot of passes conservatively assume this is the required condition. >>...

...s(unsigned char*) /home/brian/src/fuzzpy/llvm_src/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_coverage_libcdep.cc:467:5 #3 0x1b7b53 in fuzzer::Fuzzer::PrepareCoverageBeforeRun() /home/brian/src/fuzzpy/llvm_src//llvm/lib/Fuzzer/FuzzerLoop.cpp:264:5 #4 0x1b501b in fuzzer::Fuzzer::RunOne(std::vector<unsigned char, std::allocator<unsigned char> > const&) /home/brian/src/fuzzpy/llvm_src//llvm/lib/Fuzzer/FuzzerLoop.cpp:212:3 #5 0x1b6be3 in fuzzer::Fuzzer::ShuffleAndMinimize() /home/brian/src/fuzzpy/llvm_src//llvm/lib/Fuzzer/FuzzerLoop.cpp:195:11 #6 0x14477b in...

...g if the documentation for LoopPass > (http://llvm.org/docs/WritingAnLLVMPass.html#LoopPass) is misleading or > incorrect (or if I'm just missing something.) The documentation states: > > "The doFinalization method ... is called when the pass framework has finished > calling runOnLoop <http://llvm.org/docs/WritingAnLLVMPass.html#runOnLoop> for > every loop in the program being compiled." > > From this, I understood that for a single instance of a LoopPass sub-class, the > doFinalization method would be called exactly once, after all loops had been &gt...

I'm wondering if the documentation for LoopPass ( http://llvm.org/docs/WritingAnLLVMPass.html#LoopPass) is misleading or incorrect (or if I'm just missing something.) The documentation states: "The doFinalization method ... is called when the pass framework has finished calling runOnLoop<http://llvm.org/docs/WritingAnLLVMPass.html#runOnLoop> for every loop in the program being compiled." >From this, I understood that for a single instance of a LoopPass sub-class, the doFinalization method would be called exactly once, after all loops had been seen. However in pra...

...an/src/fuzzpy/llvm_src/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_coverage_libcdep.cc:467:5 >> #3 0x1b7b53 in fuzzer::Fuzzer::PrepareCoverageBeforeRun() >> /home/brian/src/fuzzpy/llvm_src//llvm/lib/Fuzzer/FuzzerLoop.cpp:264:5 >> #4 0x1b501b in fuzzer::Fuzzer::RunOne(std::vector<unsigned char, >> std::allocator<unsigned char> > const&) >> /home/brian/src/fuzzpy/llvm_src//llvm/lib/Fuzzer/FuzzerLoop.cpp:212:3 >> #5 0x1b6be3 in fuzzer::Fuzzer::ShuffleAndMinimize() >> /home/brian/src/fuzzpy/llvm_src//llvm/lib/Fuzzer/Fuzz...

...number of bytes used to store a type. > > > > Read the document on Writing an LLVM Pass > > (http://llvm.org/docs/WritingAnLLVMPass.html) to learn how to have your > > pass declare the TargetData pass as a prerequisite and to get a pointer > > to it when your > > runOnFunction/runOnModule/runOnBasicBlock/runOn<whatever> method is > > called. Then use the doxygen documentation to find the correct method > > of the TargetData pass > > (http://llvm.org/doxygen/classllvm_1_1TargetData.html) to use to get the > > size of the type that yo...

Hello, I would just like to ask if it's possible to explicitly free allocas. This is because I need to call functions that take structs of different sizes as input, (possibly inside of loops) and I would rather avoid a stack overflow. If this is not possible, an alternate solution would be for me to allocate an array of bytes larger than all the struct types I may be using, and cast that

...lvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_coverage_libcdep.cc:467:5 >>>> #3 0x1b7b53 in fuzzer::Fuzzer::PrepareCoverageBeforeRun() >>>> /home/brian/src/fuzzpy/llvm_src//llvm/lib/Fuzzer/FuzzerLoop.cpp:264:5 >>>> #4 0x1b501b in fuzzer::Fuzzer::RunOne(std::vector<unsigned char, >>>> std::allocator<unsigned char> > const&) >>>> /home/brian/src/fuzzpy/llvm_src//llvm/lib/Fuzzer/FuzzerLoop.cpp:212:3 >>>> #5 0x1b6be3 in fuzzer::Fuzzer::ShuffleAndMinimize() >>>> /home/brian/src/fuzzp...

...ations, but that's scary). If you wanted to do that, it would be fine. Be aware that the code generators are set up as function passes though, so you would have to insert all function prototypes in the doInitialization(...) method of the function pass: you can't just do it on the fly from runOn*Function. The real reason that we aren't doing this currently is that we don't want code generators to be hacking on the LLVM module. This greatly interferes with JIT-style multi-pass optimization and other things. Unfortunately, we are a long way from this though, as the lowering passes...

Chris Lattner wrote: > > Second, MO_ExternalSymbol is used for storing name of external > > variable/function, right? Why it's not possible to use MO_GlobalAddress, > > where returned GlobalValue* has isExternal set to true? The > > GlobalValue::getName would return the name of the symbol. > > Using the GlobalValue is certainly the preferred way if you have it.