public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Paolo Carlini <paolo.carlini@oracle.com>
Cc: Matthew Wahab <matthew.wahab@arm.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
		"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH][libstdc++][Testsuite] isctype test fails for newlib.
Date: Mon, 02 Feb 2015 16:33:00 -0000	[thread overview]
Message-ID: <CAH6eHdQNytx0NCcZEPUBorenk+f=8BE86BSGiJ7=FpXZFYuL3A@mail.gmail.com> (raw)
In-Reply-To: <54CFA31F.9020601@oracle.com>

On 2 February 2015 at 16:17, Paolo Carlini <paolo.carlini@oracle.com> wrote:
> Hi,
>
> On 02/02/2015 04:49 PM, Matthew Wahab wrote:
>>
>> Hello,
>>
>> With target arm-none-eabi, the libstdc++ tests
>> 28_regex/traits/char/isctype.cc and 28_regex/traits/wchar/isctype.cc fail at
>> --
>> VERIFY(!t.isctype('\n', t.lookup_classname(range(blank))));
>> --
>> This is because libstdc++ puts '\n' in the 'space' character class, rather
>> than 'blank' when building on newlib. This problem was known when suport for
>> the blank character class was added to libstdc++ (see
>> https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01902.html) so this failure
>> is not unexpected.
>>
>> Changes to newlib that would have allowed the problem to be fixed were
>> made (https://sourceware.org/ml/newlib/2009/msg00342.html) but then reverted
>> (https://sourceware.org/ml/newlib/2009/msg00438.html).
>>
>> This patch modifies the test to add a special case for the behaviour with
>> newlib.
>>
>> Tested by running check-target-libstdc++-v3 -
>> libstdc++-dg/conformance.exp, with the modified tests, for arm-none-eabi and
>> aarch64-none-linux-gnu. No new failures and the modified tests now pass on
>> arm-none-eabi.
>>
>> Ok for trunk?

This is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64467 so please
note that in the ChangeLog.

> I guess the patch is Ok for trunk, but please also add in the comment a link
> to this message of yours, that is
> https://gcc.gnu.org/ml/gcc-patches/2015-02/msg00059.html.
>
> Thanks,
> Paolo.
>
> PS: please remember to always CC libstdc++-v3 patches to
> libstdc++@gcc.gnu.org.

Yes, not everyone subscribes to gcc-patches so please always send
libstdc++ patches to the libstdc++ list, as documented at
https://gcc.gnu.org/lists.html and in the libstdc++ manual.

  reply	other threads:[~2015-02-02 16:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 15:49 Matthew Wahab
2015-02-02 16:17 ` Paolo Carlini
2015-02-02 16:33   ` Jonathan Wakely [this message]
     [not found]     ` <54CFBBD5.4080205@arm.com>
2015-02-02 18:14       ` Jonathan Wakely
2015-02-03 10:17     ` Matthew Wahab
2015-02-03 10:27       ` Paolo Carlini
2015-02-03 10:40         ` Matthew Wahab
2015-02-03 11:17           ` Paolo Carlini
2015-02-07  0:12           ` Jonathan Wakely
2015-02-09 11:25             ` Matthew Wahab
2015-02-09 13:18               ` Hans-Peter Nilsson
2015-02-09 17:50                 ` Matthew Wahab
     [not found]                 ` <54D8F2F6.7030406@arm.com>
     [not found]                   ` <alpine.BSF.2.02.1502091814490.19399@arjuna.pair.com>
2015-02-10  8:51                     ` Matthew Wahab
2015-02-11 11:14                       ` Matthew Wahab
2015-02-11 15:44                         ` Jonathan Wakely
2015-02-13 13:48                           ` Matthew Wahab
2015-03-09 12:47                             ` Jonathan Wakely
2015-03-10  9:56                               ` Matthew Wahab

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='CAH6eHdQNytx0NCcZEPUBorenk+f=8BE86BSGiJ7=FpXZFYuL3A@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=matthew.wahab@arm.com \
    --cc=paolo.carlini@oracle.com \
    /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).