public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pacoarjonilla at yahoo dot es" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/104640] incomplete unicode support for User-defined literals
Date: Wed, 27 Apr 2022 02:12:05 +0000	[thread overview]
Message-ID: <bug-104640-4-y2o6UZ0xsG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104640-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Paco Arjonilla <pacoarjonilla at yahoo dot es> ---
(In reply to Paco Arjonilla from comment #2)

Compiler output:

<source>:4:17: error: pasting """_" and "\U000000b5m" does not give a valid
preprocessing token
    4 | double operator ""_##suffix (long long unsigned arg) \
      |                 ^~~
<source>:11:1: note: in expansion of macro 'MACRO'
   11 | MACRO(µm) // <-- COMPILATION ERROR (should compile)
      | ^~~~~
<source>:11:7: error: expected initializer before '\U000000b5m'
   11 | MACRO(µm) // <-- COMPILATION ERROR (should compile)
      |       ^~
<source>:4:22: note: in definition of macro 'MACRO'
    4 | double operator ""_##suffix (long long unsigned arg) \
      |                      ^~~~~~

  parent reply	other threads:[~2022-04-27  2:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 14:15 [Bug c++/104640] New: " maik.urbannek at cattatech dot de
2022-02-24  0:32 ` [Bug preprocessor/104640] " pinskia at gcc dot gnu.org
2022-04-26 15:41 ` pacoarjonilla at yahoo dot es
2022-04-27  2:12 ` pacoarjonilla at yahoo dot es [this message]
2022-06-10 19:13 ` lhyatt 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-104640-4-y2o6UZ0xsG@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).