public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: james.bannon@ntlworld.com
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/10535: No specialisations for wchar_t in std::string or std::ostream?
Date: Tue, 29 Apr 2003 10:26:00 -0000 [thread overview]
Message-ID: <20030429102247.26395.qmail@sources.redhat.com> (raw)
>Number: 10535
>Category: libstdc++
>Synopsis: No specialisations for wchar_t in std::string or std::ostream?
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Apr 29 10:26:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: James Bannon
>Release: libstdc++-V3.2.1
>Organization:
>Environment:
I've repeated this on the following:
MinGW GCC 3.2 (mingw special 20020817-1) and the latest release canditate.
Cygwin (latest from the mirror)
>Description:
Unable to instantiate a specialisation for wchar_t for std::string or std::ostream. I believe I am doing everything correctly. I also believe it's a generic problem with the GNU stdlib rather than the Cygwin or MinGW versions since I believe they are built from the same sources? I have also tried the latest GNU release configured under Cygwin with the same results.
>How-To-Repeat:
See the attached file.
>Fix:
See the attached file for a possible workaround?
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="Exercise0-2.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Exercise0-2.cpp"
Ly8gQWNjZWxlcmF0ZWQgQysrIENoYXB0ZXIgMCBFeGVyY2lzZSAwLTINCi8vDQovLyBKYW1lcyBC
YW5ub24gMjkvMDQvMDMgMDk6MzkNCi8vDQovLyBXcml0ZSBhIHByb2dyYW0gdGhhdCB3aGVuIHJ1
biB3cml0ZXMNCi8vICAgIFRoaXMgKCIpIGlzIGEgcXVvdGUsIGFuZCB0aGlzIChcKSBpcyBhIGJh
Y2tzbGFzaC4NCi8vDQovLyBUd28gdmVyc2lvbnM6DQovLyAgICB0ZXN0IHdpdGggc3RhbmRhcmQg
Y2hhcmFjdGVyIHN0cmVhbXMgKHR5cGUgY2hhcik7DQovLyAgICB0ZXN0IHdpdGggd2lkZSBjaGFy
YWN0ZXIgc3RyZWFtcyAodHlwZSB3Y2hhcl90KS4NCi8vDQovLyBDb21waWxlcjoNCi8vICAgIEdD
QyAzLjIgKG1pbmd3IHNwZWNpYWwgMjAwMjA4MTctMSkNCg0KI2luY2x1ZGUgPGlvc3RyZWFtPg0K
DQojaWYgU1RBTkRBUkRfU1RSRUFNICAvLyBDb21waWxlcyB3aXRob3V0IGFueSBwcm9ibGVtIGF0
IGFsbC4NCg0KaW50IG1haW4oKQ0Kew0KICAgc3RkOjpjb3V0IDw8ICJUaGlzIChcIikgaXMgYSBx
dW90ZSwgYW5kIHRoaXMgKFxcKSBpcyBhIGJhY2tzbGFzaC4iIDw8IHN0ZDo6ZW5kbDsNCn0NCg0K
I2Vsc2UgLy8gV2lkZSBjaGFyYWN0ZXIgc3RyZWFtIC0tIGRvZXNuJ3Qgd29yay4gTm8gZGVmaW5p
dGlvbiBvZiB3Y291dCBpbiBuYW1lc3BhY2Ugc3RkLg0KICAgICAgLy8gVGhlIHNhbWUgdGhpbmcg
aGFwcGVucyB3aXRoIHRoZSBsYXRlc3QgcmVsZWFzZSBjYW5kaWRhdGUgYW5kIHVuZGVyIEN5Z3dp
bi4NCiAgICAgIC8vIFRoZSBTdGFuZGFyZCBMaWJyYXJ5IHZlcnNpb24gaXMgbGlic3RkYysrLVYz
IGluIGJvdGggY2FzZXMuDQoNCmludCBtYWluKCkNCnsNCiAgIHN0ZDo6d2NvdXQgPDwgTCJUaGlz
IChcIikgaXMgYSBxdW90ZSwgYW5kIHRoaXMgKFxcKSBpcyBhIGJhY2tzbGFzaC4iIDw8IHN0ZDo6
ZW5kbDsNCn0NCg0KI2VuZGlmDQo=
reply other threads:[~2003-04-29 10:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030429102247.26395.qmail@sources.redhat.com \
--to=james.bannon@ntlworld.com \
--cc=gcc-gnats@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).