This is the mail archive of the gcc@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: More fp bug in egcs



  In message <m0yWMtF-000268C@ocean.lucon.org>you write:
  > > 
  > > One reason for keeping output reloads, even though the register is dead, 
  > is
  > > for debugging purposes.  With your patch, it looks like debugging of 
  > > unoptimized code would not work right.  It would be OK to do this
  > > when optimizing, but that would not fix the x86 bug.
  > > 
  > 
  > If the register is clobbered, isn't the value in it random? If it is
  > tru, how can it help debugging? I changed my patch to omit the output
  > reload if it is in the source and is clobbered. Does it look safe?
>From the compiler's standpoint it is clobbered.

However, the value in the clobbered register might have meaning to
the user that is debugging code.

jeff


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