> The aggressive loop optimizations definitely break Judy. It regularly > exceeds defined array bounds.
Rats! It's bad enough that anything made of software useful rusts over time (even in normal use). The last few years I worked, I couldn't believe it when I heard that the decision had been made years ago (even C99?) to CONSCIOUSLY break perfectly good old software "in the name of optimization" by making strict aliasing the default. I found webpages describing the ongoing battles between the legacy-maintaining practitioners and the max-optimizing theoreticians, who apparently won. I spent a fair bit of time as a contractor trying to understand and fix aliasing warnings for Avago in tens (or was it hundreds) of thousands of lines of important legacy software that never (or hardly ever) actually broke, but it was deemed too risky to ignore the warnings. Cheers, Alan Silverstein ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Judy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/judy-devel
