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++/63199] Inserting std::wregex to std::vector loses some std::wregex values
Date: Thu, 02 Oct 2014 16:51:00 -0000	[thread overview]
Message-ID: <bug-63199-4-7xt37Xg1K7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63199-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Tim Shen <timshen at gcc dot gnu.org> ---
Author: timshen
Date: Thu Oct  2 16:50:39 2014
New Revision: 215805

URL: https://gcc.gnu.org/viewcvs?rev=215805&root=gcc&view=rev
Log:
    PR libstdc++/63199
    * include/bits/regex.h (basic_regex::basic_regex, basic_regex::assign,
    basic_regex::swap): Fix dangling _M_traits reference problem.
    * testsuite/28_regex/algorithms/regex_match/ecma/wchar_t/63199.cc:
    New test case.

Added:
   
branches/gcc-4_9-branch/libstdc++-v3/testsuite/28_regex/algorithms/regex_match/ecma/wchar_t/63199.cc
Modified:
    branches/gcc-4_9-branch/libstdc++-v3/ChangeLog
    branches/gcc-4_9-branch/libstdc++-v3/include/bits/regex.h


  parent reply	other threads:[~2014-10-02 16:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-07 17:56 [Bug libstdc++/63199] New: Inserting std::wregex to std::vector looses " stefan at schweter dot it
2014-09-07 17:56 ` [Bug libstdc++/63199] " stefan at schweter dot it
2014-09-08  8:46 ` [Bug libstdc++/63199] Inserting std::wregex to std::vector loses " redi at gcc dot gnu.org
2014-09-25  4:44 ` timshen at gcc dot gnu.org
2014-10-02 16:51 ` timshen at gcc dot gnu.org [this message]
2014-11-28 20:25 ` timshen at gcc dot gnu.org
2023-07-20 10:29 ` 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-63199-4-7xt37Xg1K7@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).