public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org To: axiong@ca.ibm.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: libstdc++/9378: 64-bit g++: construct base:std::moneypunct_byname<char>->memory fault Date: Wed, 29 Jan 2003 21:05:00 -0000 [thread overview] Message-ID: <20030129210511.4436.qmail@sources.redhat.com> (raw) Synopsis: 64-bit g++: construct base:std::moneypunct_byname<char>->memory fault State-Changed-From-To: open->feedback State-Changed-By: bkoz State-Changed-When: Wed Jan 29 21:05:10 2003 State-Changed-Why: Thanks for the IBM guys being so quick on this one. For your compilation errors, talk to Mr. Modra or Janis, they'll be able to point you to compilers that work. As for your code, Janis is correct. The behavior reported: What's supposed to happen here? With mainline, for both 32-bit and native 64-bit powerpc64-linux I get: elm3b10% a.out terminate called after throwing an instance of 'std::runtime_error' what(): attempt to create locale from unknown name Aborted Is correct. Here's why: ISO 14882: 22.1.1.2 locale ctors and dtors throws: runtime_error if the argument is ont valid, or is null. The set of valid string argument values is "C", "", and any implementation-defined values. In the above case, you're trying to create a locale based on the implementation-defined value of "abc." The GNU implemenation defines this value to be junk, and errors out. (Correctly so, I think.) Current libstdc++/g++ combos are more strict on this than other C++ libraries (namely, ones that only do one locale.) This was an issue in some commerical C++ library validators until the above was pointed out to them. best, benjamin http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9378
next reply other threads:[~2003-01-29 21:05 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-29 21:05 bkoz [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-12 11:23 steven 2003-01-30 1:56 Martin Sebor 2003-01-30 1:56 Benjamin Kosnik 2003-01-30 1:36 Benjamin Kosnik 2003-01-29 21:26 Martin Sebor 2003-01-21 21:36 axiong 2003-01-21 20:06 Janis Johnson 2003-01-21 6:26 Alan Modra 2003-01-20 20:26 axiong
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=20030129210511.4436.qmail@sources.redhat.com \ --to=bkoz@gcc.gnu.org \ --cc=axiong@ca.ibm.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).