public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/100904] New: [9/10/11 Regression] Wrong line location #include error "No such file or directory" – line + 1 [traditional mode as used by gfortran] Date: Fri, 04 Jun 2021 16:22:36 +0000 [thread overview] Message-ID: <bug-100904-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100904 Bug ID: 100904 Summary: [9/10/11 Regression] Wrong line location #include error "No such file or directory" – line + 1 [traditional mode as used by gfortran] Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org Target Milestone: --- Working: GCC 6 Failing since: GCC 7 * * * echo '#include "nonExisting.h"' > file.c echo '#include "nonExisting.h"' > file.F90 will give the wrong error location with: gfortran file.F90 or gcc -traditional-cpp file.c Namely: file.c:2:2: fatal error: nonExisting.h: No such file or directory Expected: Some line location in line 1. For instance, GCC 6 shows: file.c:1:0: fatal error: nonExisting.h: No such file or directory #include "nonexisting.h" * * * NOTE: gfortran only supports the traditional mode (as Fortran syntax and C syntax does not mix well without additional cpp tweaking). In C/C++, it works in non-traditional mode.
next reply other threads:[~2021-06-04 16:22 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-04 16:22 burnus at gcc dot gnu.org [this message] 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 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@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).