From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 8942C384800A; Fri,  4 Jun 2021 16:22:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8942C384800A
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBsaWJnY2MvMTAwOTA0XSBOZXc6IFs5LzEwLzExIFJlZ3Jl?=
 =?UTF-8?B?c3Npb25dIFdyb25nIGxpbmUgbG9jYXRpb24gI2luY2x1ZGUgZXJyb3IgIk5v?=
 =?UTF-8?B?IHN1Y2ggZmlsZSBvciBkaXJlY3RvcnkiIOKAkyBsaW5lICsgMSBbdHJhZGl0?=
 =?UTF-8?B?aW9uYWwgbW9kZSBhcyB1c2VkIGJ5IGdmb3J0cmFuXQ==?=
Date: Fri, 04 Jun 2021 16:22:36 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 keywords bug_severity priority component assigned_to reporter
 target_milestone
Message-ID: <bug-100904-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jun 2021 16:22:36 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100904

            Bug ID: 100904
           Summary: [9/10/11 Regression] Wrong line location #include
                    error "No such file or directory" =E2=80=93 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.=