* Re: [Fortran,4.9/5/6 Regression]ICE for Fortran files when specifying a file instead of an include directory
@ 2016-02-23 14:52 Dominique d'Humières
0 siblings, 0 replies; 2+ messages in thread
From: Dominique d'Humières @ 2016-02-23 14:52 UTC (permalink / raw)
To: Jerry DeLisle; +Cc: fortran, gcc-patches
Hi Jerry,
> Let me no if any objections.
The test gfortran.dg/include_6.f90 should be updated:
before the patch
f951: Warning: 'gfortran.log' is not a directory
after
f951: Fatal Error: 'gfortran.log' is not a directory
Thanks,
Dominique
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Fortran,4.9/5/6 Regression]ICE for Fortran files when specifying a file instead of an include directory
@ 2016-02-22 22:26 Jerry DeLisle
0 siblings, 0 replies; 2+ messages in thread
From: Jerry DeLisle @ 2016-02-22 22:26 UTC (permalink / raw)
To: gfortran; +Cc: gcc patches
The ice on this one is actually in libcpp but I don't want to mess around in
that area. Not sure why we were only doing a warning here.
I plan to commit the following to trunk with a ChangeLog entry under the simple
and obvious rule.
Let me no if any objections.
Jerry
diff --git a/gcc/fortran/scanner.c b/gcc/fortran/scanner.c
index c1d79457..c4e7974e 100644
--- a/gcc/fortran/scanner.c
+++ b/gcc/fortran/scanner.c
@@ -336,7 +336,7 @@ add_path_to_list (gfc_directorylist **list, const char *path,
}
else if (!S_ISDIR (st.st_mode))
{
- gfc_warning_now (0, "%qs is not a directory", path);
+ gfc_fatal_error ("%qs is not a directory", path);
return;
}
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-02-23 14:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-02-23 14:52 [Fortran,4.9/5/6 Regression]ICE for Fortran files when specifying a file instead of an include directory Dominique d'Humières
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 22:26 Jerry DeLisle
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).