Dug up this historic example from glibc of why optimizing compilers are a necessary mitigation against hideous code: https://sourceware.org/git/?p=glibc.git;a=blob;f=string/strstr.c;hb=0ecb606cb6cf65de1d9fc8a919bceb4be476c602 …
-
-
The naive algo performs fine for finding "bxxx" in "[^b]{10000}bxxx", awful for finding "bxxx" in "(bxx){10000}xxx".
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
(Of course musl's code density is considerably higher, but it even has more/better comments than the old naive glibc one, I think... ;-)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.