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++/63775] [C++11] Regex range with leading dash (-) not working Date: Fri, 05 Jun 2015 04:59:00 -0000 [thread overview] Message-ID: <bug-63775-4-oF5SZQPby2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63775-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63775 --- Comment #4 from Tim Shen <timshen at gcc dot gnu.org> --- Author: timshen Date: Fri Jun 5 04:58:26 2015 New Revision: 224144 URL: https://gcc.gnu.org/viewcvs?rev=224144&root=gcc&view=rev Log: PR libstdc++/66359 Backport from mainline 2014-11-13 Tim Shen <timshen@google.com> PR libstdc++/63775 * include/bits/regex_compiler.h (_Compiler<>::_M_expression_term, _BracketMatcher<>::_M_make_range): Throw regex_erorr on invalid range like [z-a]. Change _M_expression_term interface. * include/bits/regex_compiler.tcc ( _Compiler<>::_M_insert_bracket_matcher, _Compiler<>::_M_expression_term): Rewrite bracket expression parsing. * testsuite/28_regex/algorithms/regex_match/cstring_bracket_01.cc: Add testcases and move file out of extended. Added: branches/gcc-4_9-branch/libstdc++-v3/testsuite/28_regex/algorithms/regex_match/cstring_bracket_01.cc Removed: branches/gcc-4_9-branch/libstdc++-v3/testsuite/28_regex/algorithms/regex_match/extended/cstring_bracket_01.cc Modified: branches/gcc-4_9-branch/libstdc++-v3/ChangeLog branches/gcc-4_9-branch/libstdc++-v3/include/bits/regex_compiler.h branches/gcc-4_9-branch/libstdc++-v3/include/bits/regex_compiler.tcc
next prev parent reply other threads:[~2015-06-05 4:59 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-07 18:33 [Bug c++/63775] New: " gnu-org at bignm dot com 2014-11-08 9:23 ` [Bug libstdc++/63775] " timshen at gcc dot gnu.org 2014-11-13 7:40 ` timshen at gcc dot gnu.org 2015-06-05 4:59 ` timshen at gcc dot gnu.org [this message] 2023-07-20 11:32 ` 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-63775-4-oF5SZQPby2@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).