public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/59283] missing std::basic_string constructor
[not found] <bug-59283-4@http.gcc.gnu.org/bugzilla/>
@ 2013-11-25 12:26 ` redi at gcc dot gnu.org
2014-01-29 15:42 ` redi at gcc dot gnu.org
1 sibling, 0 replies; 2+ messages in thread
From: redi at gcc dot gnu.org @ 2013-11-25 12:26 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59283
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is a known issue. Our std::string does not support the C++11 allocator
requirements, and the current implementation probably never will. When we
switch to a non-Copy-On-Write std::string it will include C++11 allocator
support.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug libstdc++/59283] missing std::basic_string constructor
[not found] <bug-59283-4@http.gcc.gnu.org/bugzilla/>
2013-11-25 12:26 ` [Bug libstdc++/59283] missing std::basic_string constructor redi at gcc dot gnu.org
@ 2014-01-29 15:42 ` redi at gcc dot gnu.org
1 sibling, 0 replies; 2+ messages in thread
From: redi at gcc dot gnu.org @ 2014-01-29 15:42 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59283
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
dup
*** This bug has been marked as a duplicate of bug 53221 ***
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-01-29 15:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-59283-4@http.gcc.gnu.org/bugzilla/>
2013-11-25 12:26 ` [Bug libstdc++/59283] missing std::basic_string constructor redi at gcc dot gnu.org
2014-01-29 15:42 ` redi at gcc dot gnu.org
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).