public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: loewis@informatik.hu-berlin.de To: gcc-gnats@gcc.gnu.org Cc: boehme@informatik.hu-berlin.de Subject: preprocessor/6780: Incorrect diagnosis of token pasting Date: Thu, 23 May 2002 03:06:00 -0000 [thread overview] Message-ID: <200205231004.g4NA4UrK009787@paros.informatik.hu-berlin.de> (raw) >Number: 6780 >Category: preprocessor >Synopsis: Incorrect diagnosis of token pasting >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu May 23 03:06:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: >Release: 3.1 >Organization: HUB >Environment: System: SunOS paros 5.9 Beta_Refresh sun4u sparc SUNW,Sun-Blade-1000 Architecture: sun4 host: sparc-sun-solaris2.8 build: sparc-sun-solaris2.8 target: sparc-sun-solaris2.8 configured with: ../configure --host=sparc-sun-solaris2.8 --enable-shared --enable-threads --with-cpu=v8 --with-gnu-ld --with-gnu-as --enable-version-specific-runtime-libs >Description: When compiling the program #define inc2(a,b) <##a##.##b##> #define INC(X) inc2(X,h) #include INC(stdio) int main() { printf("Hallo"); } gcc gives the warning warning: pasting "<stdio>" and "." does not give a valid preprocessing token This warning is incorrect: There is no token <stdio> (with starting and terminating angle bracket) created during pasting. It is not clear whether the compiler really created such a token, or whether it just reports it in the error message. >How-To-Repeat: Compile the above code. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-23 10:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-23 3:06 loewis [this message] 2002-05-23 3:50 neil 2002-05-24 12:36 neil
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=200205231004.g4NA4UrK009787@paros.informatik.hu-berlin.de \ --to=loewis@informatik.hu-berlin.de \ --cc=boehme@informatik.hu-berlin.de \ --cc=gcc-gnats@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).