public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/100904] [9/10/11/12 Regression] Wrong line location #include error "No such file or directory" – line + 1 [traditional mode as used by gfortran] Date: Tue, 08 Jun 2021 17:21:11 +0000 [thread overview] Message-ID: <bug-100904-4-0a4yFY5FDR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100904-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100904 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-06-08 CC| |jakub at gcc dot gnu.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Started with r7-1651-gac81cf0b2bf5efdd716d10d1c218eb5a17e1035b
next prev parent reply other threads:[~2021-06-08 17:21 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-04 16:22 [Bug libgcc/100904] New: [9/10/11 " burnus at gcc dot gnu.org 2021-06-07 9:09 ` [Bug preprocessor/100904] [9/10/11/12 " rguenth at gcc dot gnu.org 2021-06-08 17:21 ` jakub at gcc dot gnu.org [this message] 2021-06-08 18:28 ` jakub at gcc dot gnu.org 2021-06-10 0:25 ` dmalcolm at gcc dot gnu.org 2022-01-20 12:58 ` rguenth at gcc dot gnu.org 2022-05-27 9:45 ` [Bug preprocessor/100904] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:45 ` jakub at gcc dot gnu.org 2023-07-07 10:40 ` [Bug preprocessor/100904] [11/12/13/14 " rguenth 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-100904-4-0a4yFY5FDR@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).