public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/63776] New: [C++11] Regex collate matching not working
@ 2014-11-07 18:39 gnu-org at bignm dot com
  2014-11-08  8:35 ` [Bug libstdc++/63776] " timshen at gcc dot gnu.org
                   ` (7 more replies)
  0 siblings, 8 replies; 9+ messages in thread
From: gnu-org at bignm dot com @ 2014-11-07 18:39 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 63776
           Summary: [C++11] Regex collate matching not working
           Product: gcc
           Version: 4.9.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gnu-org at bignm dot com

Created attachment 33919
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33919&action=edit
Full test program source code

The locale has been set to "pt_BR.UTF-8" and the following String should match
the Regexp passed to the group_regexp() function. It seems as if the collation
matching is not working.

String = "João Méroço" <email@isp.com>
DEBUG: group_regexp(): Using 'c' flag
DEBUG: group_regexp(): Using 'o' flag
DEBUG: group_regexp(): Match Failed!
group_regexp('/("[[:alpha:][:space:]]+")/co') returned failure!

Full test program source code is attached below.
>From gcc-bugs-return-466007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 07 18:46:49 2014
Return-Path: <gcc-bugs-return-466007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26404 invoked by alias); 7 Nov 2014 18:46:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26381 invoked by uid 48); 7 Nov 2014 18:46:44 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/63774] wrong code at all optimization levels on x86_64-linux-gnu
Date: Fri, 07 Nov 2014 18:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63774-4-2mrap4A9DF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63774-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63774-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg00479.txt.bz2
Content-length: 209

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc774

--- Comment #3 from Marc Glisse <glisse at gcc dot gnu.org> ---
At least it was deliberate. I did wonder if anyone would complain when I wrote
the patch...


^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2015-03-09  6:49 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-11-07 18:39 [Bug c++/63776] New: [C++11] Regex collate matching not working gnu-org at bignm dot com
2014-11-08  8:35 ` [Bug libstdc++/63776] " timshen at gcc dot gnu.org
2014-11-08 10:56 ` gnu-org at bignm dot com
2014-11-10 18:26 ` redi at gcc dot gnu.org
2015-01-20 11:05 ` gnu-org at bignm dot com
2015-01-20 11:10 ` gnu-org at bignm dot com
2015-01-20 13:08 ` redi at gcc dot gnu.org
2015-02-06  6:55 ` timshen at gcc dot gnu.org
2015-03-09  6:49 ` timshen at gcc dot gnu.org

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).