search for: pimpl

Hi all, I 'd like to fetch a list of structures, and found that it could be done via LLVMContextImpl *pImpl = Context.pImpl; pImpl->AnonStructTypes This however needs the inclusion of LLVMContextImpl.h, which is not contained in the includes dir, but in the lib/IR dir (next to the .cpp files) and is not installed under /usr/local/include... Whats the reason for this? Isn't it indended to be us...

...l might actually not be very different. Marcello 2014-06-24 17:14 GMT+01:00 David Blaikie <dblaikie at gmail.com>: > What're the situation in which you need to clear it? If there are > outstanding users of it (given that you mention clients possibly > holding references to the pimpl, it sounds like you might have > outstanding users) then wouldn't they be at risk of breaking if you > mutate the LLVMContext underneath them? > > & if you don't have outstanding users, is there any particular benefit > to resetting the LLVMContext compared to just making...

On 18 Aug 2016, at 23:59, Richhiey Thomas <richhiey.thomas at gmail.com> wrote: > I've currently added a few classes which don't really belong to the public API (currently) into private headers and used PIMPL with the Cluster class. I'm having difficulty reading your changes, because you aren't keeping to one complete change per commit. So for instance you've added a new Cluster::Internal class in one commit, but started using it in a different commit in which you also make a number of othe...

> > > > Actually, you're doing something slightly unusual there: making the > internal member public. Protected would be better, and private is I think > most usual; library clients aren't going to have access to the Internal > class declaration, so they can't call things on it. This means it's > actually difficult right now to subclass Feature. > > I

...that for some reason which I'm not aware of LLVMContextImpl is actually exposed as a public pointer in the LLVMContext interface,making it publicly available to objects that use it directly (this seems to happen quite a lot in the codebase). In LLVMContext the LLVMContextImpl is contained in a pImpl pointer that is const (the pointer itself can't be changed) and I guess this is some kind of protection against object replacing the LLVMContextImpl directly, which stops us from just deleting it + getting a new one. In addition to that, being pImpl public, there is no guarantee that objects do...

...> > > 2014-06-24 17:14 GMT+01:00 David Blaikie <dblaikie at gmail.com>: > > > >> What're the situation in which you need to clear it? If there are > >> outstanding users of it (given that you mention clients possibly > >> holding references to the pimpl, it sounds like you might have > >> outstanding users) then wouldn't they be at risk of breaking if you > >> mutate the LLVMContext underneath them? > >> > >> & if you don't have outstanding users, is there any particular benefit > >> to rese...

...64> TempStr(Name); > TempStr.push_back('.'); > raw_svector_ostream TmpStream(TempStr); > unsigned NameSize = Name.size(); > > do { > TempStr.resize(NameSize + 1); > TmpStream.resync(); > TmpStream << getContext().pImpl->NamedStructTypesUniqueID++; > > Entry = &getContext().pImpl-> > NamedStructTypes.GetOrCreateValue(TmpStream.str()); > } while (Entry->getValue()); > } > > > — > Mehdi > >> On Jun 2, 2015, at 11:23 AM, Haopeng...

...the other things you mentioned in your mail soon. Thanks for the information on the documentation that will be required. Currently, as you had mentioned that pruning the API for hiding implementation of things that are not part of the public API is an important thing to do. So I was looking at how PIMPL has been adopted in Xapian, and if I'm not wrong, this has been done with the Internal class. But I hadn't written the API in a way to agree with that design. Any tips or guidelines I could get in order to make the current API conform with PIMPL as implemented in Xapian? Thanks. Regards,...

Hi All, I generated the following code with "clang -flto" command. void test(struct StruTyName *a) { ... } Then the type of test function is "void (%struct.StruTyName.100*)" by calling function::getFunctionType API. What's the meaning of number 100? Best, Haopeng

...sh_back('.'); >>> raw_svector_ostream TmpStream(TempStr); >>> unsigned NameSize = Name.size(); >>> do { >>> TempStr.resize(NameSize + 1); >>> TmpStream.resync(); >>> TmpStream << getContext().pImpl->NamedStructTypesUniqueID++; >>> Entry = &getContext().pImpl-> >>> NamedStructTypes.GetOrCreateValue(TmpStream.str()); >>> } while (Entry->getValue()); >>> } >>> >>> >>> — >>&gt...

...umber of dimensions can be reduced, the speed of clustering can increase easily. You continued: > > > Currently, as you had mentioned that pruning the API for hiding > implementation of things that are not part of the public API is an > important thing to do. So I was looking at how PIMPL has been adopted in > Xapian, and if I'm not wrong, this has been done with the Internal class. > But I hadn't written the API in a way to agree with that design. Any tips > or guidelines I could get in order to make the current API conform with > PIMPL as implemented in Xapian?...

We have ClearCase database on unix and users on windows. We are creating Unix users locally on that Clearcase server. Samba is also installed on that server. User windows machines are part of domain. Groups,usres are created on domain and same users,groups are created on unix server. Now problem is occuring when a windows user is changing the password for his domain login. as soon as user is

Hi, I am trying to write a module pass that traverses through named structure types defined and modifies the type of certain fields in these named types. Is there any simple way of doing this? I am not quite sure how to get the LLVMContext's pImpl working from a pass since LLVMContextImpl is forward-declared. Thanks, Joe -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120814/48575773/attachment.html>

...h I'm not aware of LLVMContextImpl > is actually exposed as a public pointer in the LLVMContext interface,making > it publicly available to objects that use it directly (this seems to happen > quite a lot in the codebase). > > In LLVMContext the LLVMContextImpl is contained in a pImpl pointer that is > const (the pointer itself can't be changed) and I guess this is some kind > of protection against object replacing the LLVMContextImpl directly, which > stops us from just deleting it + getting a new one. > In addition to that, being pImpl public, there is no guara...

...;, errs()); exit(-1); } assert(M->isMaterialized() && "Module not materialized!"); PointerType *ArrayPtrTy = M->getTypeByName("struct._Array")->getPointerTo(); ``` However this piece of code crashes at Module::getTypeByName because getContext().pImpl is NULL pointer. Other similar issues include Module::getTypeByName results in a NULL pointer dereference because TheTable in StringMap is not allocated/initialized. It would be great if someone could show me what's the correct way to initialize all this kind of internal data structures so I...

...sRegistry. This *should* solve all the problems, the only > trick is > > finding every executable that uses the PassRegistry. > > How does this address the llvm_shutdown/pass derigstration issue? > > (a little more of my tale: I started trying to remove PassRegistry's > pimpl, but noticed that during pass derigstration the PassRegistry had > already been destroyed (since it's created by the first global that > tries to register a pass, so it must be destroyed before that global > in turn tries to deregister the pass) and what would happen is that > the g...

I actually had an idea about how to fix this in a relatively painless manner. Although given my experience over the past 4 days, it might not be best to call it painless without first trying :) The idea is to make a StaticPassRegistry. RegisterPass<> only touches the StaticPassRegistry, and nothing else touches the StaticPassRegistry. So once you enter main(), StaticPassRegistry can be

...2 at umd.edu> wrote: > Hi, > > I am trying to write a module pass that traverses through named structure > types defined and modifies the type of certain fields in these named types. > Is there any simple way of doing this? I am not quite sure how to get the > LLVMContext's pImpl working from a pass since LLVMContextImpl is > forward-declared. Mutating types is unsupported, and generally a bad idea. Make a new named type, then replace all the values which use that type with values which use the new type. -Eli

...performance of computer systems has been steadily increasing as faster processors, memory, and video cards are continuously being developed. The one key component that is often neglected when looking at improving the performance of a computer system is the hard drive. http://2site.com/jewgds Ass Pimples Vs Back Acne What is Back Acne ? Umm... Acne on your back. There you have it. Well there is a difference?compared to face acne . Back acne is one form of body acne and it''s a bitch to reach when you need to treat that really juicy volcanic pimple on your back. http://2site.com/cbgpay...

-------- Original Message -------- Subject: Re: [Samba] Need help in samba configuration Date: Tue, 17 Nov 2009 10:42:42 -0500 From: Brian Cowan <brcowan at gmail.com> To: Pankaj.C.Pimple at relianceada.com References: <OF3AAD32AD.86A5D538-ON65257671.002808E6-65257671.002851F0 at relianceada.com> If your Samba server is a fully operational domain member server, then the behavior you are experiencing should not be occurring. Period. Take a close look at your samba server...