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]
Other format: [Raw text]

Re: question about target info cache in resource.c


Tom de Vries <vries@codesourcery.com> writes:

> The following fix makes sure that the cached live info is invalidated:
> ...
> @@ -1865,6 +1880,7 @@ redundant_insn (rtx insn, rtx target, rt
>  		{
>  		  /* Show that this insn will be used in the sequel.  */
>  		  INSN_FROM_TARGET_P (candidate) = 0;
> +		  incr_ticks_for_insn (candidate);
>  		  return candidate;
>  		}
>
> ...
> and the assert is not triggered anymore.
>
> So my questions are:
> - is the consistency check correct? Does it make sense to fix all the
>   cases where it triggers?
> - Is my analysis of the example and the fix correct?

Sounds reasonable to me.

Ian


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