From: Tobias Burnus <Tobias_Burnus@mentor.com>
To: Harald Anlauf <anlauf@gmx.de>, <fortran@gcc.gnu.org>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: Fortran: Improve file-reading error diagnostic [PR55534] (was: Re: [Patch] Fortran: Improve -Wmissing-include-dirs warnings [PR55534])
Date: Fri, 24 Sep 2021 10:41:58 +0200 [thread overview]
Message-ID: <a3b72852-8ca9-684c-b559-d9c706eb89ec@mentor.com> (raw)
In-Reply-To: <siipui$dr9$1@ciao.gmane.io>
On 23.09.21 23:01, Harald Anlauf via Fortran wrote:
> compiled with -cpp gives:
>
> pr55534-play.f90:4:2:
>
> 4 | type t
> | 1~~~~~~
> Fatal Error: no/such/file.inc: No such file or directory
> compilation terminated.
>
> If you have an easy solution for that one,
David has an easy but hackish solution, cf. https://gcc.gnu.org/PR100904
That's a GCC 7 regression, which also affects C/C++ but only when
compiling with -traditional-cpp, which gfortran does by default but
gcc/g++ don't.
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
prev parent reply other threads:[~2021-09-24 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 13:02 [Patch] Fortran: Fix -Wno-missing-include-dirs handling [PR55534] Tobias Burnus
2021-09-17 18:45 ` Tobias Burnus
2021-09-20 20:33 ` Tobias Burnus
2021-09-20 21:33 ` Harald Anlauf
2021-09-21 19:22 ` [Patch] Fortran: Improve -Wmissing-include-dirs warnings [PR55534] Tobias Burnus
2021-09-22 9:13 ` Thomas Schwinge
2021-09-22 18:29 ` Harald Anlauf
2021-09-22 22:06 ` Fortran: Improve file-reading error diagnostic [PR55534] (was: Re: [Patch] Fortran: Improve -Wmissing-include-dirs warnings [PR55534]) Tobias Burnus
[not found] ` <siipui$dr9$1@ciao.gmane.io>
2021-09-24 8:41 ` Tobias Burnus [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=a3b72852-8ca9-684c-b559-d9c706eb89ec@mentor.com \
--to=tobias_burnus@mentor.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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: link
Be 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).