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++/64303] The regex_token_iterator's copy constructor creates an incorrect iterator
Date: Wed, 17 Dec 2014 10:27:00 -0000	[thread overview]
Message-ID: <bug-64303-4-x7mj7Fi4ve@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64303-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64303

--- Comment #2 from Tim Shen <timshen at gcc dot gnu.org> ---
Author: timshen
Date: Wed Dec 17 10:27:21 2014
New Revision: 218814

URL: https://gcc.gnu.org/viewcvs?rev=218814&root=gcc&view=rev
Log:
2014-12-17  Tim Shen  <timshen@google.com>

    PR libstdc++/64302
    PR libstdc++/64303
    Backported form mainline
    2014-12-17  Tim Shen  <timshen@google.com>

    * include/bits/regex.h (match_results::cbegin, match_results::cend,
    regex_token_iterator::regex_token_iterator,
    regex_token_iterator::_M_normalize_result): Fix match_results cbegin
    and cend and regex_token_iterator::_M_result invariant.
    * include/bits/regex.tcc: Fix regex_token_iterator::_M_result invariant.
    * testsuite/28_regex/iterators/regex_token_iterator/64303.cc: Testcase.

Added:
   
branches/gcc-4_9-branch/libstdc++-v3/testsuite/28_regex/iterators/regex_token_iterator/64303.cc
Modified:
    branches/gcc-4_9-branch/libstdc++-v3/ChangeLog
    branches/gcc-4_9-branch/libstdc++-v3/include/bits/regex.h
    branches/gcc-4_9-branch/libstdc++-v3/include/bits/regex.tcc


  parent reply	other threads:[~2014-12-17 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-14 10:38 [Bug libstdc++/64303] New: " kariya_mitsuru at hotmail dot com
2014-12-17  9:26 ` [Bug libstdc++/64303] " timshen at gcc dot gnu.org
2014-12-17 10:27 ` timshen at gcc dot gnu.org [this message]
2015-03-09  6:46 ` timshen at gcc dot gnu.org
2023-07-20 11:42 ` 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-64303-4-x7mj7Fi4ve@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: link
Be 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).