[Bug fortran/92091] Inconsistent diagnostics for INCLUDE vs. #include

2020-07-22 Thread anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92091 --- Comment #3 from anlauf at gcc dot gnu.org --- (In reply to Dominique d'Humieres from comment #2) > Am I correct to understand that #include is handled by the preprocessor? Yes. Other compilers always show the path to the included file in the

[Bug fortran/92091] Inconsistent diagnostics for INCLUDE vs. #include

2020-07-22 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92091 Dominique d'Humieres changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug fortran/92091] Inconsistent diagnostics for INCLUDE vs. #include

2019-10-14 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92091 --- Comment #1 from kargl at gcc dot gnu.org --- (In reply to anlauf from comment #0) > For files included via INCLUDE, the diagnostics printed may be incomplete > when the included file resides in a different directory. There is no > problem whe

[Bug fortran/92091] Inconsistent diagnostics for INCLUDE vs. #include

2019-10-14 Thread anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92091 anlauf at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P5 Known to fail|