On Sat, 28 Apr 2012 09:10:23 +0200, David Haller
Seconded. ISTR something much like that some time ago that also was locale (UTF-8?) specific. So, it probably is a regression or basically the same bug cropping up in a different utility.
No bug! Multibyte processing is slower, period. Either file a bug upstreams (which will be rejected as upstream doesn't don't do multibyte processing) or find ways to speed up the current i18n patch. All other bug reports on this will be closed by me as I'm the currant coreutils maintainer.
So, it's quite definitely UTF-8 related. Probably how cut parses lines to find the seperator in UTF-8 vs. 1 Byte charsets.
Of cause it is! Just look at the i18n patch that we apply and you'll see the differences. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org