This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tree-optimization/61515] [4.9/4.10 Regression] Extremely long compile time for generated code


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61515

Jeffrey A. Law <law at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |law at redhat dot com
           Assignee|unassigned at gcc dot gnu.org      |law at redhat dot com

--- Comment #12 from Jeffrey A. Law <law at redhat dot com> ---
Fundamentally we don't have a way to know what equivalences we need to
invalidate.
Invalidation is, umm, painful.  The question in my mind is why are we getting
so many invalidations to start with.  That's the first thing to look at.

Honestly though, I really wonder if handling backedges is worth the effort,
even though it's important for one benchmark.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]