public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "timshen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/63920] Any regular expression should not match an empty sequence if match_not_null is specified Date: Tue, 25 Nov 2014 05:43:00 -0000 [thread overview] Message-ID: <bug-63920-4-6j7Vs0L2s2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63920-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63920 --- Comment #2 from Tim Shen <timshen at gcc dot gnu.org> --- Author: timshen Date: Tue Nov 25 05:43:04 2014 New Revision: 218037 URL: https://gcc.gnu.org/viewcvs?rev=218037&root=gcc&view=rev Log: PR libstdc++/63920 * include/bits/regex_executor.h: Make _M_begin non const. * include/bits/regex_executor.tcc (_Executor<>::_M_search): Increase _M_begin in search algorithm, so that _M_begin is treated as "current start position" for each search iteration. * testsuite/28_regex/algorithms/regex_search/ecma/flags.cc: New testcase. Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/bits/regex_executor.h trunk/libstdc++-v3/include/bits/regex_executor.tcc trunk/libstdc++-v3/testsuite/28_regex/algorithms/regex_search/ecma/flags.cc
next prev parent reply other threads:[~2014-11-25 5:43 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-17 17:49 [Bug libstdc++/63920] New: " kariya_mitsuru at hotmail dot com 2014-11-18 18:57 ` [Bug libstdc++/63920] " kariya_mitsuru at hotmail dot com 2014-11-25 5:43 ` timshen at gcc dot gnu.org [this message] 2015-02-06 7:04 ` timshen at gcc dot gnu.org 2023-07-20 11:35 ` redi at gcc dot gnu.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-63920-4-6j7Vs0L2s2@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).