summaryrefslogtreecommitdiffstats
path: root/lib/libc/regex/engine.c
diff options
context:
space:
mode:
authormiod <miod@openbsd.org>2004-04-01 20:39:55 +0000
committermiod <miod@openbsd.org>2004-04-01 20:39:55 +0000
commitd84580875301d99e4ccd8f1d9f79a515bdec1167 (patch)
tree998cb9b1ed71dba764dcc29855b69b3809d7b4d2 /lib/libc/regex/engine.c
parentaudio/x-vorbis, ok henning@ (diff)
downloadwireguard-openbsd-d84580875301d99e4ccd8f1d9f79a515bdec1167.tar.xz
wireguard-openbsd-d84580875301d99e4ccd8f1d9f79a515bdec1167.zip
It turns out that the so-called fast ffs(3) routines were wrong, as soon as
more than one bit is set, as the ff1 instruction counts from the highest order. However, gcc/m88k with optimization enabled would use a correct, short sequence based upon ff1 and tweaks, to achieve the intended result, hence i did not catch this flaw initially. So revert to the C implementation - it is correct, still decently fast, and will only be used when compiling at -O0.
Diffstat (limited to 'lib/libc/regex/engine.c')
0 files changed, 0 insertions, 0 deletions