https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83021
Paul Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83021
--- Comment #13 from Paul Thomas ---
Author: pault
Date: Tue Nov 28 15:38:55 2017
New Revision: 255205
URL: https://gcc.gnu.org/viewcvs?rev=255205&root=gcc&view=rev
Log:
2017-11-28 Paul Thomas
PR fortran/83021
* resolve.c (re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83021
--- Comment #12 from Paul Thomas ---
Author: pault
Date: Tue Nov 28 15:13:42 2017
New Revision: 255202
URL: https://gcc.gnu.org/viewcvs?rev=255202&root=gcc&view=rev
Log:
2017-11-28 Paul Thomas
PR fortran/83021
* resolve.c (re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83021
--- Comment #11 from Jürgen Reuter ---
The ICEs are indeed with that problem.
(Duplicate ticket https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83042)
However, now I get segfaults however in several of our C and C++ bind(C)
interfaces. I do not know
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83021
Paul Thomas changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83021
--- Comment #9 from Jürgen Reuter ---
Does the reproducer in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83042
maybe help to fix this bug? At the moment our usage of the gcc trunk is frozen
as we cannot work around the many cases where it occurs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83021
Dominique d'Humieres changed:
What|Removed |Added
CC||juergen.reuter at desy dot de
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83021
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83021
Dominique d'Humieres changed:
What|Removed |Added
Summary|[7/8 Regression] gfortran |[7/8 Regression] gfortran
