Determine optimization strategy for filter code. #11

justinzane opened this Issue Apr 4, 2013 · 0 comments


None yet

1 participant


I'm not sure what to think about the attribute((optimize(3))) usage.
Have you done some benchmarking that shows that the speedup is
significant compared to the normal -O2? If yes, I guess we can keep
I don't know what to think of them either. I did a really simplist benchmark with the algorithm on my core i3 laptop initially to determine if it was useful to keep everything double or float. There was no benefit to reducing presicion on this one system, but that attribute was dramatic. Did not try O2, though, just 03 and O0. I thought about messing with vectorization, but I only have x86-64 PCs and that seems most valuable for embedded devices which I cannot test at the moment.

That was an experiment, and I will do whatever the more experienced developers recommend.

@justinzane justinzane was assigned Apr 4, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment