https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69554
--- Comment #12 from Manuel López-Ibáñez ---
(In reply to Thomas Koenig from comment #11)
> (In reply to Manuel López-Ibáñez from comment #7)
> > Please take this as a humble general suggestion: Fortran maintainers should
> > enforce during patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69554
--- Comment #11 from Thomas Koenig ---
(In reply to Manuel López-Ibáñez from comment #7)
> Please take this as a humble general suggestion: Fortran maintainers should
> enforce during patch review that any new diagnostic has a corresponding
> tes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69554
--- Comment #10 from Manuel López-Ibáñez ---
(In reply to Dominique d'Humieres from comment #8)
> This seems a lot of work for big patches. Note that this is not specific to
> gfortran: any one committing a patch should look at the Intel results!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69554
--- Comment #9 from David Malcolm ---
(In reply to Thomas Koenig from comment #5)
> No patch is needed to expose this bug.
>
> Test case:
Thanks. This is almost certainly my fault, probably due to r229884. Sorry.
I plan to fix this once I get
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69554
--- Comment #8 from Dominique d'Humieres ---
Likely caused by revision r29884.
> Please take this as a humble general suggestion: Fortran maintainers
> should enforce during patch review that any new diagnostic has
> a corresponding testcase tri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69554
Manuel López-Ibáñez changed:
What|Removed |Added
Keywords||diagnostic
Component|othe
