>>>>> Jakub Jelinek writes:
Jakub> Not sure why sched allows that, because insn 42 clearly operates on
volatile
Jakub> memory. Do you think that's a bug in sched that it should be honoring
Jakub> /v and not moving insns accross it, or that something is broken with the
Jakub> ppc* patterns?
I think it more likely is a latent bug in the scheduler, not a
problem with the patterns. Admittedly the volatile load-locked insn does
not appear until the post-reload splitter after sched1, but it still seems
that the scheduler should not move volatile mem.
What happens on Alpha? I would expect that it would show similar
symptoms.
David
