This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/24814] unrolling doesn't put loop notes in right place
- From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 7 Mar 2006 22:42:56 -0000
- Subject: [Bug rtl-optimization/24814] unrolling doesn't put loop notes in right place
- References: <bug-24814-5394@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from amylaar at gcc dot gnu dot org 2006-03-07 22:42 -------
(In reply to comment #6)
> Yes, if you need to detect loops, call the routine to detect natural loops.
> This is the way of the future.
> LOOP_NOTES are not.
Is flow_loops_find and the data that it initailizes a stable interface, and
can it be safely called from prologue/epilogue generation?
I see no mention of this function in the files in doc/ ; the loop notes
are documented there, though.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24814