FAQ
I'm inclined to reject this. I suspect that optimizing b0,b1,b2,b3 is
just tinkering around the edges: for real speed-up you need to eliminate
the bounds checking and do the equivalent of C++'s UNALIGNED_LOAD32.
Doing that will require re-writing in assembler, or at least using
package unsafe, and would remove any mention of b0,b1,b2,b3.

https://codereview.appspot.com/8360044/

--

---
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 2 | next ›
Discussion Overview
groupgolang-dev @
categoriesgo
postedApr 9, '13 at 12:13a
activeApr 9, '13 at 7:36a
posts2
users2
websitegolang.org

2 users in discussion

Nigeltao: 1 post Jan Mercl: 1 post

People

Translate

site design / logo © 2022 Grokbase