public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "richard-gccbugzilla at metafoo dot co.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99534] New: bogus UDL diagnostic for header-name followed by macro Date: Thu, 11 Mar 2021 00:07:39 +0000 [thread overview] Message-ID: <bug-99534-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99534 Bug ID: 99534 Summary: bogus UDL diagnostic for header-name followed by macro Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: richard-gccbugzilla at metafoo dot co.uk Target Milestone: --- Testcase: #define M #include "foo.h"M #include <foo.h>M This produces two warnings warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix] At least the second diagnostic appears to be incorrect: <foo.h> is not a string literal and lexically can't have a UDL suffix applied. The first diagnostic might also be incorrect (the header-name production for double-quoted strings also can't have a UDL suffix), but the max munch rule appears to require that we lex a string-literal rather than a header-name here! I think that's probably a wording bug, and the lexer should prefer to produce a header-name token whenever possible. (I'm taking that part to WG21 CWG; Clang also diagnoses this, but EDG does not.)
reply other threads:[~2021-03-11 0:07 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-99534-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).