public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/94168] New: [10 Regression] error: extended character § is not valid in an identifier since r10-3309-g7d112d6670a0e0e6 Date: Fri, 13 Mar 2020 13:44:31 +0000 [thread overview] Message-ID: <bug-94168-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94168 Bug ID: 94168 Summary: [10 Regression] error: extended character § is not valid in an identifier since r10-3309-g7d112d6670a0e0e6 Product: gcc Version: 10.0 Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: preprocessor Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org Target Milestone: --- I see the following regression: $ cat red.cc #ifdef WINDOWS § #endif $ g++-9 red.cc -c $ g++ red.cc -c red.cc:2:1: error: extended character § is not valid in an identifier 2 | �� | ^
next reply other threads:[~2020-03-13 13:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-13 13:44 marxin at gcc dot gnu.org [this message] 2020-03-13 13:45 ` [Bug preprocessor/94168] " marxin at gcc dot gnu.org 2020-03-13 16:44 ` lhyatt at gmail dot com 2020-03-13 18:16 ` joseph at codesourcery dot com 2020-03-16 8:06 ` marxin at gcc dot gnu.org 2020-03-16 10:29 ` marxin at gcc dot gnu.org 2020-04-01 7:52 ` rguenth at gcc dot gnu.org 2020-04-01 7:56 ` marxin 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-94168-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).