Community Page
- phildawes.net/blog/ Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- Hi, Do you feel that your agility in Factor has improved since this post? Roger
- Thanks for the pointer - I've cleaned up the spam and regrettably added some moderation
- I'm loving the comments thread for this post. Can't decide whether to get my upholstery cleaned or do something about my fast food obesity.
- Cool - thanks Eric
- I pasted some code that does the moving sum in factor. http://paste.factorcode.org/paste?id=569#282
Jump to original thread »
Continuing on from yesterday evening, I had a bit of time tonight in front of the telly so I implemented the rest of the fast-search functionality in factor using the assembler code from the previous post.
The first step was to create the simple bloom filter for sending to the assember code. To ... Continue reading »
The first step was to create the simple bloom filter for sending to the assember code. To ... Continue reading »
10 months ago
10 months ago
But why bother? bt r,r and bt r,i are only 1 uop on a Core2. Check the instruction timings here: http://www.agner.org/optimize/
Use mov (%eax,%edi,4), %edi and drop the shl $0x2, %edi.
10 months ago
10 months ago
> Hi Phil,
>
> I couldn't post a comment on your blog for some reason so I'm posting
> this to the list instead.
>
> The seq>hash word you write already exists in the sets vocabulary, its
> called unique.
>
> And (prepare-filter) looks nicer if you use fry:
>
> : (prepare-filter) ( filter seq -- )
> '[ 1048576 mod _ set-bit ] each ;
>
> Slava