search for: hashextras

I am trying to upgrade my code to use the latest version of llvm from svn. Whenever I include "llvm/ADT/HashExtras.h", I get error messages like the following. Does anyone know what is going on? Thanks for any help. llvm[1]: Compiling Aux.cpp for Debug build (PIC) In file included from /home/lefever/work/memrep/src/compiler/include/Aux.h:4, from Aux.cpp:1: /home/lefever/llvm/svn0910...

So, after digging around in the old llvm/ADT/hash_map, I think I discovered the problem. Now, if you want to include llvm/ADT/HashExtras.h, you have to include the hash_map h file from your system (ext/hash_map in my case) and define HASH_NAMESPACE, before you include llvm/ADT/HashExtras. It might be good to include some documentation about that for those using HashExtras. Regards, Ryan Ryan M. Lefever wrote: > I am trying...

...thod moved out of line? Please add a comment before the out-of-line body indicating why it should not be moved back inline. Analysis/AliasAnalysis.cpp: why don't you need the external stub? Does it work for you like this? namespace llvm { extern void BasicAAStub(); } include/llvm/ADT/HashExtras.h: Is pointer support already built into the intel headers, making the hash implementation unneeded? If so, please add a comment to the #ifndef indicating that. As a general comment, please keep source lines within 80 columns. Otherwise the patches look great, thanks a lot! -Chris -- http:/...

Hi, I am attempting to compile the llvm distribution with the Intel Compiler 8.0 on linux and I have some minor patches I would like to apply. In our project we compile and run the code both on win32, together with Morten Ofstad using the MS compiler, and on linux using the intel compiler. I have wrapped the extra code to make llvm compile for icc in #ifdef __INTEL_COMPILER #endif The patches

Chris, include/llvm/ADT/HashExtras.h I did some more testing on this topic: ICC complained that the last template was partially loaded and would be used to instantiate the template<> struct hash<const char *>. Rearranging the templates so that one for arbritraty pointers (inlined) comes first, works excellent for icc. E....

..._value functions for all these types (note, it hashes char * as pointers, not as strings - but char * is not used as a key anywhere in LLVM). This means that although the way of adding your own hashing functions is different, the default implementation works for 99% of all the cases and the ADT/HashExtras.h file is not necessary. BUT there is one place where llvm defines it's own hashing function, in include/llvm/Target/TargetSchedInfo.h template <> struct hash<llvm::OpCodePair> { size_t operator()(const llvm::OpCodePair& pair) const { return hash<long>()(...

...> RelativePath="..\..\include\llvm\Adt\hash_map"> > > </File> > > <File > > RelativePath="..\..\include\llvm\Adt\hash_set"> > > </File> > > <File > > RelativePath="..\..\include\llvm\Adt\HashExtras.h"> > > </File> > > <File > > RelativePath="..\..\include\llvm\Adt\ilist"> > > </File> > > <File > > RelativePath="..\..\include\llvm\Adt\iterator"> > > </File> > > &l...

...</File> > <File > RelativePath="..\..\include\llvm\Adt\hash_map"> > </File> > <File > RelativePath="..\..\include\llvm\Adt\hash_set"> > </File> > <File > RelativePath="..\..\include\llvm\Adt\HashExtras.h"> > </File> > <File > RelativePath="..\..\include\llvm\Adt\ilist"> > </File> > <File > RelativePath="..\..\include\llvm\Adt\iterator"> > </File> > <File > RelativePath="..\.....