public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/20285] [12/13/14/15 Regression] gcc -E - < . gives a misleading error message Date: Fri, 19 Jul 2024 12:53:11 +0000 [thread overview] Message-ID: <bug-20285-4-tdZHkckqMR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-20285-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20285 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|11.5 |12.5 --- Comment #24 from Richard Biener <rguenth at gcc dot gnu.org> --- GCC 11 branch is being closed.
prev parent reply other threads:[~2024-07-19 12:53 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20285-4@http.gcc.gnu.org/bugzilla/> 2011-06-27 13:48 ` [Bug preprocessor/20285] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org 2012-03-13 14:09 ` [Bug preprocessor/20285] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org 2012-07-02 13:53 ` [Bug preprocessor/20285] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org 2013-04-12 15:17 ` [Bug preprocessor/20285] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2014-06-12 13:45 ` [Bug preprocessor/20285] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:28 ` [Bug preprocessor/20285] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-06-23 8:21 ` [Bug preprocessor/20285] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 19:57 ` [Bug preprocessor/20285] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:29 ` jakub at gcc dot gnu.org 2021-05-14 9:45 ` [Bug preprocessor/20285] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:03 ` rguenth at gcc dot gnu.org 2022-05-27 9:33 ` [Bug preprocessor/20285] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:28 ` jakub at gcc dot gnu.org 2023-07-07 10:28 ` [Bug preprocessor/20285] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-07-19 12:53 ` rguenth at gcc dot gnu.org [this message]
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-20285-4-tdZHkckqMR@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).