public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "z0sh at sogetthis dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/49952] New: Unicode literals do not generate errors as prescribed by the FDIS standard Date: Tue, 02 Aug 2011 22:09:00 -0000 [thread overview] Message-ID: <bug-49952-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49952 Summary: Unicode literals do not generate errors as prescribed by the FDIS standard Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: trivial Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: z0sh@sogetthis.com Host: Linux x86 Referring to the standard: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2442.htm The character literal \UNNNNNNNN must only accept characters in the range 0-0x10FFFF, excluding surrogates. However, GCC allows 31-bit values above 0x10FFFF. To wit, the following compiles: char32_t s[] = U"\U0010FFFF\U7FFFFFFF"; It may be that the actual wording of the FDIS (2.3.2, p.19) is more relaxed than in the reference I gave above and that this behaviour is in fact intentional, but I thought I bring it up anyway.
next reply other threads:[~2011-08-02 22:09 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-02 22:09 z0sh at sogetthis dot com [this message] 2011-08-02 22:32 ` [Bug c++/49952] [C++0x] " paolo.carlini at oracle dot com 2011-08-03 11:19 ` joseph at codesourcery dot com 2011-08-03 11:37 ` z0sh at sogetthis dot com 2011-08-03 12:01 ` paolo.carlini at oracle dot com 2021-12-02 2:29 ` pinskia 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-49952-4@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: linkBe 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).