loop-2{f,g} failures

[Jeffrey A Law]

  In message < 19980826102017.C29439@dgii.com >you write:
  > I have been adding another x86 target (essentially a SVR5-based target)
  > and trying to analyze two new failures that I haven't been seeing on
  > other similar x86 targets.  Linux doesn't fail.  OpenServer doesn't fail.
  > Unixware 2 doesn't fail.
  > 
  > The tests in question were loop-2f and loop-2g.  Now I see these exact
  > tests failing on Sparc/Solaris tests.  I think this means I can pretty
  > much quit staring at my new target-specific files. :-)
  > 
  > Can anyone briefly comment on these failures?  Are these known to be
  > fragile? In all the mmap voodoo in those test cases, have we perhaps
  > introduced a dependence on library/mmap/vm behaviour?
They're designed to tickle very obscure bugs in the loop optimizer.
It's unlikely they're bugs in your backend.

jeff