This is the mail archive of the
mailing list for the GCC project.
Re: reg_scan info validity during jump
- To: Richard Henderson <rth at cygnus dot com>
- Subject: Re: reg_scan info validity during jump
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Sat, 11 Jul 1998 01:25:24 -0600
- cc: "David S. Miller" <davem at dm dot cobaltmicro dot com>, Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>, meissner at cygnus dot com, egcs-patches at cygnus dot com
- Reply-To: law at cygnus dot com
In message <19980711003058.A9249@dot.cygnus.com>you write:
> > Anyway I think the better patch is to simply not copy the loop exit
> > code if it references a register higher than max_reg_num. Yes we
> > miss some opts, but calling reg_scan like that is very heavyweight.
> As I mentioned to Dave, I think the proper solution is to have
> incremental update functions to call, a-la record_base_value.
That is certainly the right way to go long term. But do we want
to fart with that now when all we have to do is return 0 if the
register is >= max_reg?