News for hackers. Stuff that matters.

A comment on Reducing the Performance Impact of Debug Code in C Libraries.

Re:Reducing the Performance Impact of Debug Code in C Libraries by angryredblock on Wednesday November 16, 2016 @09:08AM (#12966891)
Was it the boolean check that degraded performance or was branch misprediction inside a nested loop the root cause?

The solution you came to seems quite elegant but I'd be curious to see metrics with the debug_on check moved outside both loops.

[ Parent | on HN ]
Re:Reducing the Performance Impact of Debug Code in C Libraries by tasn on Saturday November 19, 2016 @09:38AM (#12993648)
I accidentally posted my reply as a top-comment and it's now too late to change it.

Sorry about that.

[ Parent | on HN ]