public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/48340] Several wchar_t tests FAIL on IRIX 6.5
Date: Wed, 30 Mar 2011 11:50:00 -0000 [thread overview]
Message-ID: <bug-48340-4-UpwlGIW3eP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48340-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48340
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-03-30 11:27:09 UTC ---
(In reply to comment #5)
> > --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-03-30 11:07:13 UTC ---
> > Are you using a specific configure value for --enable-clocale or just using the
> > default "generic" model?
>
> I'm using the generic model: last time I tried ieee_1003.1-2001 (both on
> Solaris and IRIX), it failed (PR libstdc++/41495) and I haven't yet
> gotten around to do anything about this.
Yep.
> > What about this test, I assume the assertion fails:
>
> Indeed.
>
> > What is the value of _ISspace in /usr/include/ctype.h ?
>
> #define _ISspace (_S | _BL)
>
> #define _S 0x00000008 /* Spacing character */
> #define _BL 0x80000000 /* The blank character class */
>
> > If it's greater than (1<<15) that would explain it
>
> There we have it.
Badabing.
I'm planning to add isblank to std::locale (LWG 2019) which will need changes
to all the locale models so while I'm doing that I will overhaul the ieee
locale model (possibly adding a POSIX 2008 version as well, which would be
close to the gnu model) and I'll also address this, so we can handle values
over (1<<15). Currently that '15' maximum is hardcoded in a few places.
next prev parent reply other threads:[~2011-03-30 11:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 17:32 [Bug libstdc++/48340] New: " ro at gcc dot gnu.org
2011-03-29 18:19 ` [Bug libstdc++/48340] " redi at gcc dot gnu.org
2011-03-29 18:48 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-03-29 18:48 ` redi at gcc dot gnu.org
2011-03-30 11:27 ` redi at gcc dot gnu.org
2011-03-30 11:29 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-03-30 11:50 ` redi at gcc dot gnu.org [this message]
2011-03-30 11:55 ` redi at gcc dot gnu.org
2011-03-30 15:17 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-03-30 15:17 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-04-03 17:58 ` redi at gcc dot gnu.org
2011-04-06 8:55 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-11 16:18 ` ro at gcc dot gnu.org
2012-01-11 16:28 ` redi at gcc dot gnu.org
2012-01-11 16:30 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-06-13 11:44 ` ro 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-48340-4-UpwlGIW3eP@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).