public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sourceware.org Subject: [Bug regex/20095] parse_dup_op duplicates the tree exponentially when using repeated + Date: Thu, 24 Aug 2023 20:21:35 +0000 [thread overview] Message-ID: <bug-20095-132-Iyj2lFtrEO@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-20095-132@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=20095 Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adhemerval.zanella at linaro dot o | |rg --- Comment #4 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- I am not sure who exactly GNU grep handles this since it also uses gnulib regex code. Is this code really being tested by GNU grep? I deleted the fil, make check, and it seems not to affect the test's outcome. I also tried to sync with gnulib master, but it also does not help. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-24 20:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-05-14 1:08 [Bug regex/20095] New: " dualbus at gmail dot com 2020-04-15 15:53 ` [Bug regex/20095] " dpmendenhall at gmail dot com 2023-08-24 15:14 ` jwakely.gcc at gmail dot com 2023-08-24 20:21 ` adhemerval.zanella at linaro dot org [this message] 2023-08-24 20:28 ` jwakely.gcc at gmail dot com 2023-08-24 22:43 ` sh200105 at mail dot ru
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-20095-132-Iyj2lFtrEO@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs-regex@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).