This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: hpux20 pointer optimization bug
- To: Jim Wilson <wilson at cygnus dot com>
- Subject: Re: hpux20 pointer optimization bug
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 09 Jun 1998 00:25:43 -0600
- cc: tprince at cat dot e-mail dot com, egcs-patches at cygnus dot com, tprince at computer dot org
- Reply-To: law at cygnus dot com
In message <199806090003.RAA09062@rtl.cygnus.com>you write:
> The same reasoning doesn't apply to the same field, but it does seem like
> a reasonable solution. I don't see anything else using the `same' field
> during or after loop unrolling, so it should be harmless to clear it to fix
> this bug. If we add future optimizations to loop though, it might be useful
> to retain this info if we can.
Sounds reasonable.
> Alternatively, I think we could also fix the problem by moving the code that
> sets the unrollled field. loop.h says:
> unsigned unrolled : 1; /* 1 if new register has been allocated in
> unrolled loop. */
> We could redefine that to `allocated and initialized'. I think this patch
> gives the same effect as your patch while leaving the same field set.
This seems just as reasonable too. If we take this approach, I would
recommend we update the comment in loop.h.
> I don't think it makes much difference which way the problem is fixed thoug.
Likewise. unroll.c is yours, so it's your call.
Thanks,
jeff