public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lhyatt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/103902] GCC requires a space between string-literal and identifier in a literal-operator-id where the identifier is not in basic character set
Date: Tue, 28 Jun 2022 15:22:20 +0000	[thread overview]
Message-ID: <bug-103902-4-0elacWSa7W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103902-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Lewis Hyatt <lhyatt at gcc dot gnu.org> ---
(In reply to Lewis Hyatt from comment #3)
> I can look into that.

Patch waiting for review here:
https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596660.html

  parent reply	other threads:[~2022-06-28 15:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04  9:24 [Bug c++/103902] New: Only the addition space between string-literal and identifier in a literal-operator-id will be accepted by GCC where the identifier is not in a " xmh970252187 at gmail dot com
2022-01-04 23:07 ` [Bug preprocessor/103902] GCC requires a space between string-literal and identifier in a literal-operator-id where the identifier is not in " pinskia at gcc dot gnu.org
2022-06-10 19:13 ` lhyatt at gcc dot gnu.org
2022-06-10 19:14 ` lhyatt at gcc dot gnu.org
2022-06-28 15:22 ` lhyatt at gcc dot gnu.org [this message]
2023-02-08 17:42 ` pinskia at gcc dot gnu.org
2023-07-19  3:59 ` cvs-commit at gcc dot gnu.org
2023-07-19  4:02 ` lhyatt at gcc dot gnu.org
2023-07-20  0:23 ` thiago.bauermann at linaro dot org
2023-07-20  1:11 ` lhyatt at gcc dot gnu.org
2023-07-20  1:14 ` thiago.bauermann at linaro dot org
2023-07-20  3:21 ` cvs-commit at gcc dot gnu.org
2023-07-20 16:24 ` thiago.bauermann at linaro dot 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-103902-4-0elacWSa7W@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).