public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Matthew Wahab <matthew.wahab@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	       libstdc++ <libstdc++@gcc.gnu.org>,
	       Hans-Peter Nilsson <hp@bitrange.com>
Subject: Re: [PATCH][libstdc++][Testsuite] isctype test fails for newlib.
Date: Mon, 09 Mar 2015 12:47:00 -0000	[thread overview]
Message-ID: <20150309124746.GD21227@redhat.com> (raw)
In-Reply-To: <54DE00B5.6010003@arm.com>

[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]

On 13/02/15 13:48 +0000, Matthew Wahab wrote:
>On 11/02/15 15:43, Jonathan Wakely wrote:
>>On 11/02/15 11:14 +0000, Matthew Wahab wrote:
>>>Attached the fixed patch.
>>>Tested by running check-target-libstdc++-v3, with the modified tests,
>>>for arm-none-eabi and aarch64-none-linux-gnu.
>>>
>>>Ok to commit?
>>
>>OK, thanks.
>
>Some DOS line endings were introduced into the char/isctype.cc file 
>when I committed this change These aren't visible in a terminal or 
>with svn diff but do show up in emacs. This is causing the test to 
>fail in local runs. The wchar_t/isctype.cc file isn't affected.
>
>I've committed the attached patch as obvious, it just removes the DOS 
>line endings from the file.

That patch still left DOS line-endings in the file.

The test also now fails for newlib targets not using
--enable-clocale=newlib so I'm just going to disable the check for
'\n' entirely, since it doesn't have consistent behaviour on newlib.

Tested x86_64-linux, committed to trunk. Hopefully we can finally
close this one for good!



[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 1662 bytes --]

commit 923ba4238cc715051fa97441c0cca23245289f23
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Mar 9 10:26:03 2015 +0000

    	PR libstdc++/64467
    	* testsuite/28_regex/traits/char/isctype.cc: Don't test newline
    	for newlib targets. Really fix mixed line-endings this time.

diff --git a/libstdc++-v3/testsuite/28_regex/traits/char/isctype.cc b/libstdc++-v3/testsuite/28_regex/traits/char/isctype.cc
index 8f71910..62d3740 100644
--- a/libstdc++-v3/testsuite/28_regex/traits/char/isctype.cc
+++ b/libstdc++-v3/testsuite/28_regex/traits/char/isctype.cc
@@ -1,9 +1,9 @@
-// { dg-do run }
-// { dg-options "-std=gnu++11" }
-// { dg-additional-options "-DNEWLINE_IN_CLASS_BLANK" { target newlib } }
-
-//
-// 2010-06-23  Stephen M. Webb <stephen.webb@bregmasoft.ca>
+// { dg-do run }
+// { dg-options "-std=gnu++11" }
+// { dg-additional-options "-DNEWLINE_IN_CLASS_BLANK" { target newlib } }
+
+//
+// 2010-06-23  Stephen M. Webb <stephen.webb@bregmasoft.ca>
 //
 // Copyright (C) 2010-2015 Free Software Foundation, Inc.
 //
@@ -54,11 +54,7 @@ test01()
   VERIFY(!t.isctype('_', t.lookup_classname(range(digit))));
   VERIFY( t.isctype(' ', t.lookup_classname(range(blank))));
   VERIFY( t.isctype('\t', t.lookup_classname(range(blank))));
-#if defined (NEWLINE_IN_CLASS_BLANK)
-  /* On some targets, '\n' is in class 'blank'.
-     See https://gcc.gnu.org/ml/gcc-patches/2015-02/msg00059.html.  */
-  VERIFY( t.isctype('\n', t.lookup_classname(range(blank))));
-#else
+#if !defined (NEWLINE_IN_CLASS_BLANK)
   VERIFY(!t.isctype('\n', t.lookup_classname(range(blank))));
 #endif
   VERIFY( t.isctype('t', t.lookup_classname(range(upper), true)));

  reply	other threads:[~2015-03-09 12:47 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
     [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 [this message]
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=20150309124746.GD21227@redhat.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hp@bitrange.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=matthew.wahab@arm.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).