public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wcs84014 at xcoxc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/107089] New: Line-terminating '\' leaves the characters when the next-line is a multi-line comment
Date: Thu, 29 Sep 2022 17:47:50 +0000	[thread overview]
Message-ID: <bug-107089-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107089
           Summary: Line-terminating '\' leaves the characters when the
                    next-line is a multi-line comment
           Product: gcc
           Version: 11.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: preprocessor
          Assignee: unassigned at gcc dot gnu.org
          Reporter: wcs84014 at xcoxc dot com
  Target Milestone: ---

I found it when I tried to use the CPP as a general-purpose macro.

~$ gcc -v
Target: x86_64-linux-gnu /gcc version 11.2.0 (Debian 11.2.0-13)

~$ cat a.c
1=\
//xyz
ok*/

2=\
/*xyz
NG*/

3=\(sp)(nl)
/*xyz
NG*/

4=\
//*xyz
ok:gcc NG:-traditional*/


~$ cat a.c | cpp -P -C -nostdinc  #-traditional-cpp
1=//xyz
ok*/
2=/*xyz
z
NG*/
<stdin>:9:3: warning: backslash and newline separated by space
3=/*xyz
yz
NG*/
4=//*xyz
ok:gcc NG:-traditional*/

             reply	other threads:[~2022-09-29 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 17:47 wcs84014 at xcoxc dot com [this message]
2022-09-29 22:42 ` [Bug preprocessor/107089] " pinskia at gcc dot gnu.org
2022-09-30  2:35 ` wcs84014 at xcoxc dot com
2022-10-06 10:00 ` wcs84014 at xcoxc dot com

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