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++/64585] The basic_regex object should not match any character sequence after a call to basic_regex::imbue Date: Mon, 19 Jan 2015 22:56:00 -0000 [thread overview] Message-ID: <bug-64585-4-j922nMlGj8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64585-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64585 --- Comment #1 from Tim Shen <timshen at gcc dot gnu.org> --- Author: timshen Date: Mon Jan 19 22:56:04 2015 New Revision: 219865 URL: https://gcc.gnu.org/viewcvs?rev=219865&root=gcc&view=rev Log: PR libstdc++/64584 PR libstdc++/64585 * include/bits/regex.h (basic_regex<>::basic_regex, basic_regex<>::assign, basic_regex<>::imbue, basic_regex<>::swap, basic_regex<>::mark_count): Drop NFA after imbuing basic_regex; Make assign() transactional against exception. * include/bits/regex_compiler.h (__compile_nfa<>): Add back __compile_nfa SFINAE. * include/std/regex: Adjust include order to avoid __compile_nfa forward declaration. * testsuite/28_regex/basic_regex/assign/char/string.cc: New testcase. * testsuite/28_regex/basic_regex/imbue/string.cc: New testcase. Added: trunk/libstdc++-v3/testsuite/28_regex/basic_regex/imbue/ trunk/libstdc++-v3/testsuite/28_regex/basic_regex/imbue/string.cc Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/bits/regex.h trunk/libstdc++-v3/include/bits/regex_compiler.h trunk/libstdc++-v3/include/std/regex trunk/libstdc++-v3/testsuite/28_regex/basic_regex/assign/char/string.cc
next prev parent reply other threads:[~2015-01-19 22:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-13 17:22 [Bug libstdc++/64585] New: " kariya_mitsuru at hotmail dot com 2015-01-19 22:56 ` timshen at gcc dot gnu.org [this message] 2015-01-19 23:09 ` [Bug libstdc++/64585] " timshen at gcc dot gnu.org 2015-03-09 6:52 ` timshen at gcc dot gnu.org 2023-07-20 11:44 ` 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-64585-4-j922nMlGj8@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).