search for: passb

hi all, i have some thing not so sure about "scope" of llvm passes: suppose i have a function pass PassF and a BasicBlock analysis pass PassB. if i want to use the analysis result of PassB for a BasicBlock in PassF, i think i can create PassB in runOnFunction of PassF, and call runOnBasicBlock manually to get the result: PassB pb; //create a PassB //we also need consider the analysis usage of PassB pb.runOnBasicBlock(bb); // run PassB o...

Hello, this is a question, concerning cmake lists configuration. I am trying to link together two llvm passes, but they still should be as two modules. So: passA - A.so passB - B.so passB should use passA , so I sould use target_link_libraries ( and of course, I have included useAnalysis in passB) . But I can't link libraries that are build as Modules, so I tried to create two libraries at once ; A.a(static) and A.so (llvm does not allow to create shared libraries)...

...lt;criswell at uiuc.edu> wrote: > >> ether zhhb wrote: >> >>> hi all, >>> >>> i have some thing not so sure about "scope" of llvm passes: >>> >>> suppose i have a function pass PassF and a BasicBlock analysis pass >>> PassB. if i want to use the analysis result of PassB for a BasicBlock in >>> PassF, i think i can create PassB in runOnFunction of PassF, and call >>> runOnBasicBlock manually to get the result: >>> >>> PassB pb; //create a PassB >>> //we also need consider th...

We have discovered the issue with our code. It seems that when the first call to doInitilization utilized one of the specified analyses, that analysis had never been properly added as required. Using gdb, we can see that addRequired is getting called (seen below) but when doInitalization is finally called, it still responds as if the analysis was not required. Is this a bug or is

Hey all, We have been working on a pass that uses another pass to count loads and stores prior to performing its own instrumentation. The second pass adds the first as required via the usual getAnalysisUsage function. On one machine, it has been tested and proven to function correctly. On another machine, whenever the second pass is run, it consistently fails the assertion: opt:

..., can't replicate existing data > > > > It appears that this could be having an effect on replication, but it's > > unclear because the secondary/replica doesn't see much traffic. > > > > Authentication is via PAM and the system is Gentoo Linux x86_64. passb > > driver = pam, userdb driver = static . > > > > doveadm user -u '*' shows the system users listed twice like this (is > > this a problem?) and then prints: > > > > ---- > > reuben > > liam > > reuben > > liam > &gt...

...ecot[7698]: replicator: Error: listing users failed, can't replicate existing data It appears that this could be having an effect on replication, but it's unclear because the secondary/replica doesn't see much traffic. Authentication is via PAM and the system is Gentoo Linux x86_64. passb driver = pam, userdb driver = static . doveadm user -u '*' shows the system users listed twice like this (is this a problem?) and then prints: ---- reuben liam reuben liam <some other users> Error: User listing returned failure Fatal: user listing failed ---- To me that doesn'...

...; ?> It appears that this could be having an effect on replication, >>> but it's >>> ?> unclear because the secondary/replica doesn't see much traffic. >>> ?> >>> ?> Authentication is via PAM and the system is Gentoo Linux x86_64. >>> passb >>> ?> driver = pam, userdb driver = static . >>> ?> >>> ?> doveadm user -u '*' shows the system users listed twice like this >>> (is >>> ?> this a problem?) and then prints: >>> ?> >>> ?> ---- >>> ?&g...

...r: > listing users failed, can't replicate existing data > > It appears that this could be having an effect on replication, but it's > unclear because the secondary/replica doesn't see much traffic. > > Authentication is via PAM and the system is Gentoo Linux x86_64. passb > driver = pam, userdb driver = static . > > doveadm user -u '*' shows the system users listed twice like this (is > this a problem?) and then prints: > > ---- > reuben > liam > reuben > liam > <some other users> > Error: User listing returned fai...

...g an effect on replication, >>>>> but it's >>>>> ??> unclear because the secondary/replica doesn't see much traffic. >>>>> ??> >>>>> ??> Authentication is via PAM and the system is Gentoo Linux x86_64. >>>>> passb >>>>> ??> driver = pam, userdb driver = static . >>>>> ??> >>>>> ??> doveadm user -u '*' shows the system users listed twice like this >>>>> (is >>>>> ??> this a problem?) and then prints: >>>&gt...

...t replicate existing data >>> >>> It appears that this could be having an effect on replication, but it's >>> unclear because the secondary/replica doesn't see much traffic. >>> >>> Authentication is via PAM and the system is Gentoo Linux x86_64. passb >>> driver = pam, userdb driver = static . >>> >>> doveadm user -u '*' shows the system users listed twice like this (is >>> this a problem?) and then prints: >>> >>> ---- >>> reuben >>> liam >>> reuben >&gt...

...?> unclear because the secondary/replica doesn't see much >>>>>>> traffic. >>>>>>> ???> >>>>>>> ???> Authentication is via PAM and the system is Gentoo Linux >>>>>>> x86_64. >>>>>>> passb >>>>>>> ???> driver = pam, userdb driver = static . >>>>>>> ???> >>>>>>> ???> doveadm user -u '*' shows the system users listed twice >>>>>>> like this >>>>>>> (is >>>&...

...a doesn't see much >>>>>>>>> traffic. >>>>>>>>> ????> >>>>>>>>> ????> Authentication is via PAM and the system is Gentoo Linux >>>>>>>>> x86_64. >>>>>>>>> passb >>>>>>>>> ????> driver = pam, userdb driver = static . >>>>>>>>> ????> >>>>>>>>> ????> doveadm user -u '*' shows the system users listed twice >>>>>>>>> like this >>&gt...

...data >> ?> >> ?> It appears that this could be having an effect on replication, but >> it's >> ?> unclear because the secondary/replica doesn't see much traffic. >> ?> >> ?> Authentication is via PAM and the system is Gentoo Linux x86_64. passb >> ?> driver = pam, userdb driver = static . >> ?> >> ?> doveadm user -u '*' shows the system users listed twice like this (is >> ?> this a problem?) and then prints: >> ?> >> ?> ---- >> ?> reuben >> ?> liam >> ?&...

...this could be having an effect on replication, >>>> but it's >>>> ?> unclear because the secondary/replica doesn't see much traffic. >>>> ?> >>>> ?> Authentication is via PAM and the system is Gentoo Linux x86_64. >>>> passb >>>> ?> driver = pam, userdb driver = static . >>>> ?> >>>> ?> doveadm user -u '*' shows the system users listed twice like this >>>> (is >>>> ?> this a problem?) and then prints: >>>> ?> >>&gt...

...; >? > It appears that this could be having an effect on replication, >> but it's >> >? > unclear because the secondary/replica doesn't see much traffic. >> >? > >> >? > Authentication is via PAM and the system is Gentoo Linux x86_64. >> passb >> >? > driver = pam, userdb driver = static . >> >? > >> >? > doveadm user -u '*' shows the system users listed twice like >> this (is >> >? > this a problem?) and then prints: >> >? > >> >? > ---- >> >?...

...ion, >>>>>> but it's >>>>>> ??> unclear because the secondary/replica doesn't see much traffic. >>>>>> ??> >>>>>> ??> Authentication is via PAM and the system is Gentoo Linux x86_64. >>>>>> passb >>>>>> ??> driver = pam, userdb driver = static . >>>>>> ??> >>>>>> ??> doveadm user -u '*' shows the system users listed twice like this >>>>>> (is >>>>>> ??> this a problem?) and then...

...the secondary/replica doesn't see much >>>>>>>> traffic. >>>>>>>> ???> >>>>>>>> ???> Authentication is via PAM and the system is Gentoo Linux >>>>>>>> x86_64. >>>>>>>> passb >>>>>>>> ???> driver = pam, userdb driver = static . >>>>>>>> ???> >>>>>>>> ???> doveadm user -u '*' shows the system users listed twice >>>>>>>> like this >>>>>>&gt...

Hello, Third version of the NUMA placement series Xen 4.2. All the comments received during v2''s review have been addressed (more details in single changelogs). The most notable changes are the following: - the libxl_cpumap --> libxl_bitmap renaming has been rebased on top of the recent patches that allows us to allocate bitmaps of different sizes; - the heuristics for deciding