Re: Current CVS source on m68k-next-nextstep3 chokes on first stage2compile with segmentation violation

[Toon Moene <toon at moene dot indiv dot nluug dot nl>]

I wrote:

>  Using the current CVS source (in fact, the problem has
>  been there for over a day) on m68k-next-nextstep3, I get
>  the following segmentation violation on the first stage2
>  compile:

[ ... etc. ... ]

I managed to "solve" this by removing (i.e. patch -R'ing) the  
following change by Jim Wilson:

Wed Mar 18 12:43:20 1998  Jim Wilson  <wilson@cygnus.com>

        * loop.c (struct movable): New field move_insn_first.
        (scan_loop): In consec sets code, set it.  Clear it otherwise.
        (move_movables): In consec sets code, use it.  Copy  
REG_NOTES from
        p to i1 only if i1 does not have REG_NOTES.  Delete  
obsolete ifdefed
        out code.

This is most probably not the appropriate fix; unfortunately, I  
didn't manage to find out what was wrong with the change as such -  
the fault could also simply be another bug triggered by this change.

HTH,
Toon.