This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/79165] 100% compile-time increase for polyhedron aermod by r244581
- From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 26 Jan 2017 20:15:53 +0000
- Subject: [Bug fortran/79165] 100% compile-time increase for polyhedron aermod by r244581
- Auto-submitted: auto-generated
- References: <bug-79165-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79165
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Assignee|dmalcolm at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #22 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #18)
> I wonder if it's worth injecting the equivalent of
> -fno-diagnostics-show-caret
> into the Fortran FE for when it's throwing away diagnostics, perhaps by
> turning
> gfc_buffer_error's bool flag into a tri-state:
> * unbuffered
> * buffered
> * discarderd
Given that the slowdown is fixed, I believe that attempting this optimization
is the only remaining part of this bug. I don't plan to attempt it for gcc 7.
Should the "Target Milestone" and/or "Priority" be updated?