public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64467] [5 Regression] 28_regex/traits/char/isctype.cc and wchar_t/isctype.cc
Date: Wed, 07 Jan 2015 01:06:00 -0000	[thread overview]
Message-ID: <bug-64467-4-tsoDrg1AjW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64467-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> Almost certainly r217066.
> 
> Is this a newlib target? I would expect to see the same failure for all
> newlib targets,

I verified that this is the case for mmix-knuth-mmixware and arm-eabi too, just
to eliminate my initial suspicion that this was a target bug.

> as I defined std::ctype_base::blank to be equal to
> std::ctype_base::space for newlib (and any libc where I couldn't determine
> the right bitmask for the [:blank:] character class) and the [:space:] class
> includes newline.

Uh, src/newlib/libc/include/ctype.h:

#define _B      0200
...
#define isblank(__c) \
  __extension__ ({ __typeof__ (__c) __x = (__c);                \
        (__ctype_lookup(__x)&_B) || (int) (__x) == '\t';})

(while isspace has it's own bit, "#define _S      010")
HTH. :)

But that might not be very helpful, I'm just not sure how to help.


  parent reply	other threads:[~2015-01-07  1:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01 17:46 [Bug libstdc++/64467] New: " hp at gcc dot gnu.org
2015-01-01 17:48 ` [Bug libstdc++/64467] " hp at gcc dot gnu.org
2015-01-01 18:05 ` redi at gcc dot gnu.org
2015-01-05 16:32 ` hp at gcc dot gnu.org
2015-01-05 16:42 ` redi at gcc dot gnu.org
2015-01-05 17:27 ` hp at gcc dot gnu.org
2015-01-07  1:06 ` hp at gcc dot gnu.org [this message]
2015-01-09 11:20 ` rguenth at gcc dot gnu.org
2015-01-13 11:25 ` rguenth at gcc dot gnu.org
2015-02-02 16:40 ` redi at gcc dot gnu.org
2015-02-04  9:25 ` renlin at gcc dot gnu.org
2015-02-08 14:32 ` hp at gcc dot gnu.org
2015-02-20 15:00 ` redi at gcc dot gnu.org
2015-02-20 20:44 ` hp at gcc dot gnu.org
2015-02-20 21:14 ` redi at gcc dot gnu.org
2015-03-06 16:32 ` segher at gcc dot gnu.org
2015-03-06 21:23 ` segher at gcc dot gnu.org
2015-03-09 12:48 ` redi at gcc dot gnu.org
2015-03-09 13:02 ` 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-64467-4-tsoDrg1AjW@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).