This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: reg_scan info validity during jump



  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?

jeff



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]