https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113291
Jeffrey A. Law changed:
What|Removed |Added
Priority|P1 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113291
--- Comment #8 from Jan Hubicka ---
I am not sure this ought to be P1:
- the compilation technically is finite, but not in reasonable time
- it is possible to adjust the testcas (do early inlining manually) and get
same infinite build on relea
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113291
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |hubicka at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113291
--- Comment #6 from Jan Hubicka ---
Created attachment 57427
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57427&action=edit
patch
The patch makes compilation to finish in reasonable time.
I ended up in need to dropping DISREGARD_INLINE_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113291
--- Comment #5 from Jan Hubicka ---
There is a cap in want_inline_self_recursive_call_p which gives up on inlining
after reaching max recursive inlining depth of 8. Problem is that the tree here
is too wide. After early inlining f0 contains 4 ca
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113291
--- Comment #4 from Jan Hubicka ---
There is a cap in want_inline_self_recursive_call_p which gives up on inlining
after reaching max recursive inlining depth of 8. Problem is that the tree here
is too wide. After early inlining f0 contains 4 ca
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113291
--- Comment #3 from Richard Biener ---
We're endlessly inlining during IPA. Honza, please have a look.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113291
Jakub Jelinek changed:
What|Removed |Added
Keywords|needs-bisection |
CC|
