search for: priorityqueu

...might also be useful to enable this function merging with ThinLTO). At the moment, this fingerprint is just a map of opcode -> number of occurrences in the function, which is just a ~64-int-array. Then, for each functions being considered for a merge, I'm able to rank the candidates with a PriorityQueue. Hopefully, we are able to do that in a very lightweight manner. After that, the more expensive bit will be actually performing the merge and then checking for profitability, using the TTI for code-size. I haven't given much thought about adapting this infrastructure for the SLP Vectorizer,...

...-I/opt/local/lib/ruby/1.8/i686-darwin8.5.2 -I. -O -pipe -I/opt/local/include -c libstemmer.c gcc -fno-common -O -pipe -I/opt/local/include -fno-common -pipe -fno-common -I. -I/opt/local/lib/ruby/1.8/i686-darwin8.5.2 -I/opt/local/lib/ruby/1.8/i686-darwin8.5.2 -I. -O -pipe -I/opt/local/include -c priorityqueue.c gcc -fno-common -O -pipe -I/opt/local/include -fno-common -pipe -fno-common -I. -I/opt/local/lib/ruby/1.8/i686-darwin8.5.2 -I/opt/local/lib/ruby/1.8/i686-darwin8.5.2 -I. -O -pipe -I/opt/local/include -c q_boolean.c gcc -fno-common -O -pipe -I/opt/local/include -fno-common -pipe -fno-common...

I was trying to install ferret 0.9.2 on solaris (SunOS 5.8) which does not have a sys/dir.h nix_io.c:5:21: sys/dir.h: No such file or directory make: *** [nix_io.o] Error 1 I couldn''t find an obvious way around this... any suggestions? Thanks, Rich Marisa Cornell Information Technologies Cornell University

...present. + virtual void runPasses() = 0; + + // TODO: Figure out a reasonable data access strategy, might just be + // iterators and potentionally returning vectors. The actual storage + // is thankfully flexible, so for instance in the case of LoopPasses, we + // should be able to use a PriorityQueue and not have that explode in our + // faces. +}; To me, the most logical class hierarchy looks like this: Pass ModulePass CallGraphSCCPass FunctionPass BasicBlockPass ... All of the high-level behaviors of passes are captured by which Pass class they inherit from....

...cal/lib/ruby/1.8/i686-darwin8.10.3 -I. -fno-common -g -O2 -fno-common -pipe -fno-common -D_FILE_OFFSET_BITS=64 -c posh.c gcc -I. -I/usr/local/lib/ruby/1.8/i686-darwin8.10.3 -I/usr/local/lib/ruby/1.8/i686-darwin8.10.3 -I. -fno-common -g -O2 -fno-common -pipe -fno-common -D_FILE_OFFSET_BITS=64 -c priorityqueue.c gcc -I. -I/usr/local/lib/ruby/1.8/i686-darwin8.10.3 -I/usr/local/lib/ruby/1.8/i686-darwin8.10.3 -I. -fno-common -g -O2 -fno-common -pipe -fno-common -D_FILE_OFFSET_BITS=64 -c q_boolean.c gcc -I. -I/usr/local/lib/ruby/1.8/i686-darwin8.10.3 -I/usr/local/lib/ruby/1.8/i686-darwin8.10.3 -I. -fno-c...

The patch below basically hammers out some ideas as to where I'd like to take the passmanager in LLVM. I've tried thinking things through, but I'm still a n00b, so some criticism would be more than welcome. =) Starting from line 191 down. If you're wondering why I created a patch, well that's because I found thinking in passmanagert.h the most productive. -- Regards.

...nf.rb install ferret creating Makefile make gcc -fPIC -g -O2 -fno-common -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -c q_filtered_query.c gcc -fPIC -g -O2 -fno-common -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -c priorityqueue.c gcc -fPIC -g -O2 -fno-common -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -c hashset.c gcc -fPIC -g -O2 -fno-common -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -c helper.c gcc -fPIC -g -O2 -fno-common -I. -I/usr/...

Hi everyone, I'm currently working on a new function merging optimization that is more general than the current LLVM function merging optimization that works only on identical functions. I would like to know if the community has any interest in having a more powerful function merging optimization. ---- More Details ---- Up until now, I have been focusing on the quality of the code

...void runPasses() = 0; > + > + // TODO: Figure out a reasonable data access strategy, might just be > + // iterators and potentionally returning vectors. The actual storage > + // is thankfully flexible, so for instance in the case of LoopPasses, we > + // should be able to use a PriorityQueue and not have that explode in our > + // faces. > +}; > > To me, the most logical class hierarchy looks like this: > > Pass > ModulePass > CallGraphSCCPass > FunctionPass > BasicBlockPass > ... > > All of the high-level behaviors o...

...l/llvm-2.8/include/llvm/ADT/OwningPtr.h -- Installing: /usr/local/llvm-2.8/include/llvm/ADT/PointerIntPair.h -- Installing: /usr/local/llvm-2.8/include/llvm/ADT/PointerUnion.h -- Installing: /usr/local/llvm-2.8/include/llvm/ADT/PostOrderIterator.h -- Installing: /usr/local/llvm-2.8/include/llvm/ADT/PriorityQueue.h -- Installing: /usr/local/llvm-2.8/include/llvm/ADT/SCCIterator.h -- Installing: /usr/local/llvm-2.8/include/llvm/ADT/STLExtras.h -- Installing: /usr/local/llvm-2.8/include/llvm/ADT/ScopedHashTable.h -- Installing: /usr/local/llvm-2.8/include/llvm/ADT/SetOperations.h -- Installing: /usr/local/ll...

On Thu, Sep 30, 2010 at 3:08 PM, Samuel Williams <space.ship.traveller at gmail.com> wrote: > Hi, > > I might just be doing something stupid, but when I do > > $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. > $ sudo make install > > I don't get the expected headers in >        /usr/local/llvm-2.8/include/llvm > > It is

Hi, I might just be doing something stupid, but when I do $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. $ sudo make install I don't get the expected headers in /usr/local/llvm-2.8/include/llvm It is simply an empty directory. What am I doing wrong? This is on Mac OS X, CMake 2.8+ Kind regards, Samuel

Hey guys, Now that the Lucy[1] project has Apache approval and is about to begin, the onus is no longer on Ferret to strive for Lucene compatability. (We''ll be doing that in Lucy). So I''m starting to think about ways to improve Ferret''s API. The first part that needs to be improved is the Document API. It''s annoying having to type all the attributes to