[Bug rtl-optimization/24814] unrolling doesn't put loop notes in right place

["dberlin at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #6 from dberlin at gcc dot gnu dot org  2006-03-07 21:50 -------
(In reply to comment #5)
> (In reply to comment #4)
> > Actually there is nothing that uses LOOP_NOTEs other than the old RTL loop
> > optimizer.  At least, nothing that _should_ use it.  Wanna know about loops? 
> > Find natural loops instead of depending on the notes.
> 
> So you are saying I should put natural loop detection into the SH backend so
> that it can decide if it should save all target registers?
> 
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.

I agree that this bug should be marked WONTFIX.

> It had its weaknesses, but at least it was well-tuned for a wide range of
> target architectures and operated generally well together with the rest of the
> compiler.  What we have now is a collection of passes that often work at
> cross-purposes.  E.g. web, loop strength reduction/unrolling and
> auto-increment generation are completely out of sync.

Completely irrelevant to this bug.

> 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24814