public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/104147] [9/10/11/12 Regression] C preprocessor may remove the standard required whitespace between the preprocessing tokens Date: Thu, 20 Jan 2022 20:59:10 +0000 [thread overview] Message-ID: <bug-104147-4-0yG5Kf7mKO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104147-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104147 Joseph S. Myers <jsm28 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |3.2.3 Known to work| |3.0.4 Target Milestone|--- |9.5 Status|UNCONFIRMED |NEW Last reconfirmed| |2022-01-20 Ever confirmed|0 |1 Summary|C preprocessor may remove |[9/10/11/12 Regression] C |the standard required |preprocessor may remove the |whitespace between the |standard required |preprocessing tokens |whitespace between the | |preprocessing tokens --- Comment #1 from Joseph S. Myers <jsm28 at gcc dot gnu.org> --- This appears to be a regression between GCC 3.0 and 3.2.
next prev parent reply other threads:[~2022-01-20 20:59 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-20 17:30 [Bug c/104147] New: " pavel.morozkin at gmail dot com 2022-01-20 20:59 ` jsm28 at gcc dot gnu.org [this message] 2022-01-21 7:55 ` [Bug preprocessor/104147] [9/10/11/12 Regression] " rguenth at gcc dot gnu.org 2022-01-31 14:07 ` jakub at gcc dot gnu.org 2022-01-31 14:50 ` jakub at gcc dot gnu.org 2022-02-01 19:50 ` cvs-commit at gcc dot gnu.org 2022-02-01 19:51 ` [Bug preprocessor/104147] [9/10/11 " jakub at gcc dot gnu.org 2022-02-19 8:02 ` cvs-commit at gcc dot gnu.org 2022-02-19 8:08 ` [Bug preprocessor/104147] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:23 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:24 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` jakub 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-104147-4-0yG5Kf7mKO@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).