Date: Tue, 01 Jun 2021 10:25:08 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 254763] grep very slow with 13.0-RC4 Message-ID: <bug-254763-227-JmA9PdvckY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254763-227@https.bugs.freebsd.org/bugzilla/> References: <bug-254763-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254763 --- Comment #9 from parv <parv.0zero9+freebsd@gmail.com> --- For not being noted earlier here, I will paraphrase Kyle Envans kaevans91 on Twitter ... - root issue is known in regex(3) library (see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223553 also); - grep(1) looks at each byte & for new lines; - replacing regex(3) is a huge task, requires massive time & motivation. ... I would be happy to be corrected if I had misstated. *In the mean time*, one could use instead ... - ack, textproc/p5-ack (Perl), https://github.com/beyondgrep/ack3; - ag, textproc/the_silver_searcher (C), https://github.com/ggreer/the_silver_searcher; - GNU grep, textproc/gnugrep (C), https://www.gnu.org/software/grep/; - ripgrep, textproc/ripgrep (Rust), https://github.com/BurntSushi/ripgrep. Other workaround option is to build system grep with one of external regex libraries. For that matter, one could also install GNU grep at /usr/bin. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254763-227-JmA9PdvckY>