public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sourceware.org Subject: [Bug regex/11053] Wrong results with backreferences Date: Tue, 21 Sep 2021 15:00:49 +0000 [thread overview] Message-ID: <bug-11053-132-UQuBycKGcv@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-11053-132@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=11053 --- Comment #13 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Paul Eggert <eggert@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0b5ca7c3e551e5502f3be3b06453324fe8604e82 commit 0b5ca7c3e551e5502f3be3b06453324fe8604e82 Author: Paul Eggert <eggert@cs.ucla.edu> Date: Tue Sep 21 07:47:45 2021 -0700 regex: copy back from Gnulib Copy regex-related files back from Gnulib, to fix a problem with static checking of regex calls noted by Martin Sebor. This merges the following changes: * New macro __attribute_nonnull__ in misc/sys/cdefs.h, for use later when copying other files back from Gnulib. * Use __GNULIB_CDEFS instead of __GLIBC__ when deciding whether to include bits/wordsize.h etc. * Avoid duplicate entries in epsilon closure table. * New regex.h macro _REGEX_NELTS to let regexec say that its pmatch arg should contain nmatch elts. Use that for regexec, instead of __attr_access (which is incorrect). * New regex.h macro _Attr_access_ which is like __attr_access except portable to non-glibc platforms. * Add some DEBUG_ASSERTs to pacify gcc -fanalyzer and to catch recently-fixed performance bugs if they recur. * Add Gnulib-specific stuff to port the dynarray- and lock-using parts of regex code to non-glibc platforms. * Fix glibc bug 11053. * Avoid some undefined behavior when popping an empty fail stack. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-21 15:00 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-11053-132@http.sourceware.org/bugzilla/> 2014-06-30 20:34 ` fweimer at redhat dot com 2014-06-30 20:34 ` fweimer at redhat dot com 2014-09-23 2:28 ` eggert at gnu dot org 2014-09-23 7:55 ` fweimer at redhat dot com 2017-01-17 21:24 ` eggert at gnu dot org 2021-02-06 7:37 ` eggert at cs dot ucla.edu 2021-03-04 7:33 ` mliska at suse dot cz 2021-08-16 0:55 ` sam at gentoo dot org 2021-08-16 7:08 ` simon_a_taylor at yahoo dot com 2021-08-25 5:10 ` michael.hudson at canonical dot com 2021-08-25 18:09 ` eggert at cs dot ucla.edu 2021-09-21 15:00 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-05 23:06 ` vincent-srcware at vinc17 dot net 2022-09-06 0:37 ` eggert at cs dot ucla.edu 2022-09-06 2:47 ` vincent-srcware at vinc17 dot net 2022-09-06 2:59 ` vincent-srcware at vinc17 dot net 2022-09-06 18:47 ` eggert at cs dot ucla.edu 2022-09-06 22:56 ` vincent-srcware at vinc17 dot net 2022-09-06 23:41 ` eggert at cs dot ucla.edu 2022-09-07 0:17 ` vincent-srcware at vinc17 dot net 2022-09-07 4:31 ` eggert at cs dot ucla.edu 2022-09-07 10:31 ` vincent-srcware at vinc17 dot net 2022-09-07 20:57 ` eggert at cs dot ucla.edu 2022-09-08 11:44 ` vincent-srcware at vinc17 dot net 2022-11-11 16:29 ` cvs-commit at gcc dot gnu.org 2009-12-04 19:36 [Bug regex/11053] New: Segfault on invalid backreference bonzini at gnu dot org 2010-04-09 17:46 ` [Bug regex/11053] Wrong results with backreferences bonzini at gnu dot org
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-11053-132-UQuBycKGcv@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).