Bad code generation on HPPA platform

[Jeff Law]

Steve Ellcey wrote:
> 
> The psuedo for %r8 does have REG_POINTER set and the psuedo for %r19
> does not.  I first see REG_POINTER set for ivtmp___1536 (the psuedo for
> %r8) in flow.c.138r.loop2_invariant.  This seems interesting because
> Peter's patch, that fixes this problem without undoing Andrews patch,
> includes a change to loop-invariant.c, though that change should be
> preserving REG_POINTER's during optimization not preventing them.
OK.  So what is ivtmp__1536 -- is it a pointer or an index?  Can you 
show me the gimple code which declares and uses ivtmp_1536?


Hmmm, fails for 4.3...  Hmmm, does 4.3 have POINTER_PLUS_EXPR?
(search tree.def for POINTER_PLUS_EXPR).

Jeff