RE: Insn removal.

["Virgil Palanciuc" <Virgil dot Palanciuc at cs dot pub dot ro>]

> P.S.
>    I also tried to see if there are any code sequences that
> remove the instructions 'by hand' - using something like
> NEXT_INSN (PREV_INSN (insn))= NEXT_INSN (insn) etc.
>    I didn't check very thoroughly, but AFAICT there is no such
> sequence which might affect me.

     I solved my problem. I wasn't looking closely enough to delete_insn()
in jump.c. Initially, I thought it only sets the INSN_DELETED_P flag, and
that it is not actually removing the insn.
     Anyway, I think it would have be better to have all optimization steps
call remove_insn when removing an insn is required (though I feel that even
if you agree with me on this, nobody is willing/capable to make the
modifications everywhere).

     Sorry for disturbing you and thanks again for the great help you have
been so far.

   Virgil.