similar to: [LLVMdev] Bug 1868: Specifying Pass Orderings

Devang Patel wrote: > > On Dec 17, 2007, at 2:01 PM, John Criswell wrote: > >> Devang Patel wrote: >>> >>> On Dec 17, 2007, at 1:47 PM, John Criswell wrote: >>> >>>> Dear Devang Patel, >>>> >>>> In response to your comment on bug 1868, how do I get BottomPass to >>>> requires Pass2 before Pass1? Is it by

On Dec 18, 2007, at 10:55 AM, John Criswell wrote: > Dear All, > > The attached code (which is a contrived test case) hits the following > assertion: > > test: > /home/vadve/criswell/src/llvm22/include/llvm/PassAnalysisSupport.h: > 226: > AnalysisType& llvm::Pass::getAnalysisID(const llvm::PassInfo*, > llvm::Function&) [with AnalysisType = Pass1]: Assertion

Dear All, The attached code (which is a contrived test case) hits the following assertion: test: /home/vadve/criswell/src/llvm22/include/llvm/PassAnalysisSupport.h:226: AnalysisType& llvm::Pass::getAnalysisID(const llvm::PassInfo*, llvm::Function&) [with AnalysisType = Pass1]: Assertion `ResultPass && "getAnalysis*() called on an analysis that was not "

Chris Lattner schrieb: > On Aug 21, 2009, at 3:04 AM, Marc Brünink wrote: >>> This isn't really possible. The issue is that MemDep doesn't just >>> "analyze your function". It is designed to be as lazy as possible, >>> which means that it only does analysis when a query is performed. This >>> means that if you have

Chris Lattner schrieb: > > On Aug 20, 2009, at 11:44 AM, Marc Brünink wrote: > >> Hi, >> >> I do have a FunctionPass that does change the code. This FunctionPass >> requires another FunctionPass which performs all the necessary analyses. >> This AnalysisPass again requires MemoryDependenceAnalysis. >> >> The problem is, that I would like

On Fri, Aug 21, 2009 at 10:48 AM, Marc Brünink<marc at bruenink.de> wrote: >>> actually my problem is easier. So I still have hope that it is possible: >>> >>> MemDep->Pass1->Pass2 >>> >>> Pass1 uses MemDep. Pass2 only uses Pass1. Eventually, Pass2 changes the >>> code. Unfortunately, non-local dependencies of MemDep might point to

On Aug 21, 2009, at 3:04 AM, Marc Brünink wrote: >> This isn't really possible. The issue is that MemDep doesn't just >> "analyze your function". It is designed to be as lazy as possible, >> which means that it only does analysis when a query is performed. >> This >> means that if you have MemDep->Pass1->Pass2 and Pass2 uses MemDep

Hi, I do have a FunctionPass that does change the code. This FunctionPass requires another FunctionPass which performs all the necessary analyses. This AnalysisPass again requires MemoryDependenceAnalysis. The problem is, that I would like MemoryDependenceAnalysis to run on the unaltered module. I do not want to have dependencies to changed code. What is the cleanest way to do this? Sounds

On Aug 20, 2009, at 11:44 AM, Marc Brünink wrote: > Hi, > > I do have a FunctionPass that does change the code. This FunctionPass > requires another FunctionPass which performs all the necessary > analyses. > This AnalysisPass again requires MemoryDependenceAnalysis. > > The problem is, that I would like MemoryDependenceAnalysis to run on > the > unaltered

Thanks, John. This sounds reasonable that the analysis group just provides an interface to its implementors (pass). Then I have another question, is it allowed to specify multiple pass in the same analysis group in the command line for opt? If yes, which pass will be used for the call of getAnaysis<AnalysisGroup>()? -Thomson On Mon, Jun 25, 2012 at 10:34 PM, John Criswell <criswell at

On 6/25/12 8:55 PM, Thomson wrote: > Thanks, John. > > This sounds reasonable that the analysis group just provides an > interface to its implementors (pass). Then I have another question, is > it allowed to specify multiple pass in the same analysis group in the > command line for opt? Yes, you can do that. Using multiple analysis passes that belong to the same group may

Hello all, I have written one pass to collect information about specific calls in an llvm IR file and am not trying to reference the results from the first pass in a second pass. What is the correct way to reference an additional custom pass in LLVM? At the moment the project is set up under the lib/Transforms directory in source and has the current layout: Thresholds/ include/

Hello, I have no idea how to implement the following scenario apart from running two instances of samba on the same machine... I need a setup where two different Windows users will authen- ticate with two different passwords but get mapped to the same unix user. That is JOE got password PASS1 and maps to unix user joe with uid 1000 and JACK got password PASS2 and maps to unix user joe with

Hello, I'm trying to conect two 1.6.2.13 Asterisk server with IAX. This is my configuration: Asterisk A: iax.conf register => coiax:pass1 at 69.164.207.166 [smiax] type=friend host=dynamic trunk=yes secret=pass2 context=phones deny=0.0.0.0/0.0.0.0 permit=69.164.207.166/255.255.255.255 qualify=yes Console: iax2 registry 69.164.207.166:4569 N coiax 69.164.197.105:4569

Machine is 4.8-STABLE smaug# camcontrol devlist <COMPAQ BD009122BA 3B07> at scbus0 target 0 lun 0 (pass0,da0) <COMPAQ BD009122C6 B016> at scbus0 target 1 lun 0 (pass1,da1) <COMPAQ BD009122BA 3B07> at scbus0 target 2 lun 0 (pass2,da2) <COMPAQ BD00962373 BCJE> at scbus0 target 3 lun 0 (pass3,da3) <IBM IC35L018UCPR15-0 S70H>

Asterisk-server 1 : register => hostedasterisk:pass1 at domain2.biz [BOX-YOCAN] type=user ; incoming from YOCAN... auth=rsa inkeys=Key ; pub key of user secret=XXX ; pass2 of YOCAN context=from-BOX-YOCAN ; incoming from YOCAN trunk=yes transfer=no qualify=yes [BOX-YOCAN] type=peer ; outgoing to YOCAN... host=dynamic ; registers auth=rsa outkey=kEy ; private secret key

Here is a patch to add colour to build output (make) for LLVM sources. Feedback and ideas welcome. The patch replaces $(Echo) usage in some key rules in Makefile.rules with $(Banner) which invokes a new script utils/make-banner.sh which is capable of adding appropriate ANSI escape sequences. step1: apply patch step2: chmod 755 utils/make-banner.sh step3: export MAKE_BANNER_ANSI=1 Next, you must

> On Mar 16, 2018, at 2:30 PM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote: > > Hi Vedant, > > Thank you for your reply. I think I can make this debugify-each mode, but I guess this is reserved for your GSoC project ? No, there's no reserved work. If you'd like to work on this I encourage you to do so. There's plenty of other work slated for the GSoC project.

Hi Vedant, Thank you for your reply. I think I can make this debugify-each mode, but I guess this is reserved for your GSoC project ? However, if I understand correctly, we do not want to take the output of the first check-debugify (I mean the .ll file with potentially all the WARNINGs and ERRORs after the first pass) as input for the second debugify. What we need is to take the fresh output of

Hi, I used to set up Samba password on the command line with smbpasswd using the following syntax : smbpasswd -a newuser "usersecretpasswd" smbpasswd -e newuser but it does work any more. How can I do the same without having to type in the password ? Thanks in advance. Michel